Factory docs, home
Page navigation

Pre-release documentation. Proposed designs are labelled in the page; acceptance evidence is maintained in the build review. Local paths appear as placeholders. Current state: Build review.

A milestone describes the next outcome a product owner wants, with optional guidance about achieving it. For example, "complete App Store review" can guide Tally's trajectory. This example commissions no Tally work or release. Product values, safety rules and release authority still apply.

The current draft supports recording and selecting a milestone, retaining its revisions, admitting a bounded plan and displaying dependencies and attributed forecasts. A qualified research handoff can prepare a draft from retained observations and independent review. A selected plan can also supply an implementation brief. These components have independently reviewed source proofs; the current combined installed package and full integration still need qualification.

A brief is not an implementation ticket. Automatic research, ticket admission and an overall delivery estimate are unavailable until the application supplies qualified owners for those effects. The earlier milestone design records its original proposal, not the current implementation status.

The next work is staged:

  1. Qualify the real work owner and original dispatch identity. Replaying a request after a crash must recover its original work and allowance. The existing admission issue covers shared account exposure; a plan or brief cannot grant it.
  2. Connect one selected milestone generation to that owner. Current permission, exact product and physical store must still match before admission. Superseded generations retain their history and cannot start replacement work implicitly.
  3. Connect automatic research through its separately qualified commission and retained report/review owners. Passive research reads and draft preparation can progress independently of implementation admission.
  4. Project approximate milestone and sub-objective dates from one compatible resource basis, including dependencies, queued work, outstanding exposure, reserved capacity and external review waits. Incomplete evidence produces an unknown estimate. Desired dates remain distinct from forecasts.

Maintenance, security, recovery and improvement continue under their own operating policy, whether a primary milestone exists, changes or is cancelled. Selecting a trajectory does not consume their reserves or renew a provider allowance. App Store review duration is an external uncertainty, never a promised date inferred from a ticket count.

See the current milestone objective, research handoff and implementation brief contracts.

Source: docs/explanation/milestone-trajectory.md