Implementation, publication and verification status
Implemented, merged, deployed and verified describe different facts. They are not interchangeable milestones on a single automatically advancing scale. A candidate can be published for authorized pre-launch verification before it merges; a merged change can remain unpublished; a component can be healthy while its business outcome is unverified.
Documentation status adds another independent fact. A section-reviewed article establishes source review within its declared writing scope. It does not change any product, provider or acceptance state.
Status model
Section titled “Status model”| State | Meaning | Evidence to record |
|---|---|---|
| Implemented | Behaviour exists in a named source revision | Full commit and owning code/migrations |
| Merged | Change is included in main | Merged PR and resulting main commit/tree |
| Built | Candidate output exists | Build identity, inputs and result |
| Deployed | Named component is observed at a revision | Component, target, time and source identity |
| Schema applied | Actual ledger/catalogue reflects applied definitions | Starting/resulting prefix and comparison scope |
| Scenario verified | Named action produced the expected result | Actor, target, versions, steps, observations and limits |
| Business accepted | Responsible owner accepted the scoped operational outcome | Explicit acceptance and its boundary |
Components do not advance together automatically
Section titled “Components do not advance together automatically”Frontend and API publication have separate current directories and version observations. Database migrations have another state. A frontend source SHA matching main does not show that the API or schema matches it. A static product-version label is not a substitute for the API release SHA.
The schema ledger and semantic catalogue answer different questions: migration history versus compared object definitions. A successful historical schema receipt is not a current ledger observation. The shared publication status is an input to guarded releases; it does not establish customer workflow acceptance.
Providers have independent state as well. An internal intent, queued job and local transaction do not prove the external system accepted the command. External outcomes and background states explain the receipts required at that boundary.
Source identity and combined CI
Section titled “Source identity and combined CI”GitHub can check a merge candidate containing the PR head and newer main changes. The documentation archive can identify the clean branch commit instead. Report both identities and compare relevant source inputs before reusing a result. A full-tree match can support a specific identity relationship; a similar branch name cannot.
After a squash merge, the main commit can differ from the tested branch commit even when the reviewed content is preserved. Follow the release tool’s identity/preservation contract rather than assuming one hash is every kind of identity. Publication owns the guarded transition.
Synthetic delivery statement
Section titled “Synthetic delivery statement”A synthetic delivery might say: “The access correction is implemented at candidate A; PR B merged to main C; the API reports C, while the frontend remains D; the negative cross-company and intended authorized reads passed on those observed components.” That statement is more useful than “done” because a later reader can identify which input changed.
If only local tests ran, say so. If the changed application was not published, keep that explicit. If a provider result remains uncertain, record the unresolved operation instead of turning a timeout or successful queue into completion. Known limits preserves those gaps.
Updating status without rewriting history
Section titled “Updating status without rewriting history”Use current GitHub and public version observations when resuming work. Dated receipts remain evidence of their original target and version, even after newer releases. Update current instructions when methods change; do not create a new durable process report for every routine observation or repeat a completed provider action solely to refresh a date.
The final handbook can truthfully have 85 reviewed topics while financial acceptance, operational transition and combined recovery remain open. Authority, evidence and release procedure explain how to maintain those states with precise evidence.