Canonical artifact-promotion source context
This reference preserves the boundary between temporary execution state and durable owner-governed information. It does not require one storage technology, physical cloud location, user interface, or approval workflow.
Source roles and limits
| Source | Role | Can establish | Cannot establish alone |
|---|---|---|---|
| Current PIOS framework | architecture and governance authority | source-versus-projection distinction, owner authority, five-zone state treatment, durable provenance, and the rule that producing one representation does not silently promote another into canonical truth | one universal canonical location, artifact-review threshold, or shipped promotion service |
| Historical PIOS Global at the selected revision | historical capability and architecture evidence | canonical-home purpose, working-copy distinction, review and approval states, promoted-artifact meaning, workspace cleanup dependency, and separation from Results | current Core contract, current deployment topology, or production behavior |
Restricted application evidence RAS-01 | bounded realization evidence | absence of the named historical promotion model in the searched application revision | proof that no differently named or external promotion implementation exists |
Lifecycle boundary
| Stage | Outcome | Capability or context |
|---|---|---|
| Produce work | Draft, intermediate output, or working copy exists | domain execution or derivation capability |
| Qualify result | Produced outcome is registered as execution evidence where applicable | preserve an execution result |
| Review and approve | Candidate is accepted, rejected, revised, or deferred | structured review and applicable proposal/authorization |
| Promote | Accepted content enters its designated canonical object lifecycle | promote a working artifact to canonical state |
| Clean up | Temporary workspace state is retained, archived, or removed safely | task-scoped execution-workspace lifecycle |
| Share or publish | A separate outward representation becomes accessible | sharing/publication capabilities |
A Result and a promoted artifact overlap but are not equivalent. A Result is a user-facing execution outcome; any accepted artifact may be promoted, including knowledge, configuration, documentation, or another durable object that is not presented as a Result.
Canonical-home boundary
- Canonical home is an architecture relationship: which governed object/version is authoritative for an information class.
- The promotion capability creates or revises that canonical state. It does not make “canonical home” a standalone action.
- Physical placement, PIOS-system membership, Core-contract membership, and state treatment remain separate classifications.
- A cache, working copy, generated representation, or runtime-local file does not become canonical because it is convenient or currently active.
Corpus-closure findings
The final historical gap pass assessed the repository-level overview, area indexes, documentation roadmap, terminology and inconsistency records, application state, design standards, dedicated-agent-computer context, shared-workspace principle, market surface, source log, and other architecture summaries. Their reusable requirements resolve into existing capabilities, shared elements, cross-cutting rules, deployment profiles, interface projections, project documentation, or unresolved questions, with one added Capability MLE for canonical artifact promotion.
Agent identity and capability tracking does not require a new generic CRD in this pass. Persistent identity belongs to agent-definition maintenance; runtime activity belongs to canonical events and run evidence; measurements use measurement definitions and metric observations; interpretation uses structured review; and any later agent-selection policy remains separately governed.
Application/session state, navigation, layout, terminology mapping, area indexes, wiki logs, and market entry pages are implementation, audience, documentation, or publication artifacts. They can inform profiles and presentation but do not independently satisfy the Capability MLE test.