Product Mechanics: Commands, Files, Records, and Reconstruction

1. Product mechanics preserve semantic custody

The application layer determines whether a judgment receives the intended ground, reaches the correct object, retains honest standing, waits for authority, survives termination, and becomes usable in future reasoning. Product mechanics therefore participate directly in the integrity of the intelligence system.

AIOS calls this responsibility semantic custody. Software carries purpose, context, judgment, consequence, and history across boundaries without becoming the author of what those forms mean.

A fluent model response is not enough. A successful file write is not enough. The complete product movement must preserve meaning from the person's gesture through durable settlement, visible consequence, renewal, and reconstruction.

2. One composition connects intention to reload

Each transition has an owner, an input contract, and an honest failure state. The chain begins with a human gesture or previously authorized event and ends only when durable files can reconstruct the same situation without relying on transient session memory.

This end-to-end view makes partial proof visible. A good response can still land incorrectly. A correct file can still project misleading state. An interface can look complete before writes settle. One working segment never substitutes for the composition.

3. Closed actions give work an explicit path

A closed action is the product-mechanical realization of Chapter 16's admitted-operation pattern. It carries an authorized bounded movement through declared sources, purpose-shaped context, one semantic judgment, structural validation, a named destination and standing, authority before effect, durable settlement, and projection of the resulting state.

The pattern begins from intention rather than passive inference. Background services can observe mechanical facts such as changed files, invalid syntax, or stale hashes. Semantic consequence enters through a capability whose purpose and authority are known.

Closed actions make the system both responsive and reconstructable. The operation can explain why it occurred, which ground it used, and what it was permitted to change.

4. Commands reveal capabilities; owners carry them

Commands give people named entry points for continuing thought, opening an artifact, invoking a review, advancing a plan or workflow, responding to a recommendation, commissioning work, integrating a return, registering knowledge, rebuilding a projection, inspecting lineage, or reconstructing state.

One capability can appear in several interface locations, but those surfaces converge on the same owner, source composition, contracts, writers, effects, and proof journey.

This prevents command labels, keywords, or interface position from becoming a hidden semantic router. The command identifies admitted capability; the owner preserves its full composition.

5. Each layer has one kind of responsibility

The divisions prevent mechanical custody from quietly making semantic decisions. Parsers judge form, not truth. Interfaces project state, not canonicality. Models propose meaning and consequence without directly executing irreversible effects.

The model receives implementation vocabulary only when the implementation itself is the object under analysis. Ordinary reasoning context stays in the language of purpose, sources, evidence, artifacts, and judgment.

6. File classes distribute custody

Person-owned artifacts carry documents, plans, drafts, decisions, and other work people read and edit directly. They remain useful outside the application.

Companion metadata carries identity, standing, relationships, lineage, acceptance, revision, and workflow state beside those artifacts.

Authored context regions express recurring intellectual ground in natural language. The compiler chooses the smallest complete selection for each movement.

Prompt and role assets define bounded cognitive responsibilities and response contracts.

Assignment and return records preserve commissions, granted sources, authority, products, evidence, integration state, and unresolved conditions.

Workflow and recommendation definitions preserve stages, guidance, inputs, products, follow-ons, menu relationships, and proposal semantics.

Derived registries and indexes provide rebuildable navigation, impact, search, validation, and visual projection.

Receipts and evidence establish which event occurred, what it touched, what settled, and which verification ran. The event record does not establish the semantic quality of its outcome.

7. Artifact and companion shadow form a durable pair

The canonical artifact protects human meaning and composition. The companion shadow carries operational state, lineage, source relationships, workflow position, and machine-readable custody that would damage the artifact if inserted into its prose.

The pair stays reconcilable through identity and revision. A missing artifact, orphaned shadow, ambiguous owner, or revision mismatch becomes an explicit defect attached to the affected object. Repair requires evidence; the system does not silently invent which side should govern.

8. Context compilation is a shared product capability

The compiler begins with an explicit purpose and cognitive movement, resolves declared sources, checks their standing and scope, identifies meaningful absence, selects the smallest complete ground, orders it as an intelligible composition, preserves attribution and source descent, discloses material compression loss, excludes irrelevant machinery, and records what the provider received.

This capability is shared across call sites. Rebuilding context independently inside every feature would create parallel semantic rules that drift without a visible owner.

An inspectable composition record makes context itself testable: what entered, what was omitted, why each region bore, and which resolution the judgment received.

9. Response contracts protect bridges, not conclusions

A response contract can request a judgment, rationale, assumptions, sources, uncertainty, alternatives, bounded effect proposal, or continuation options. The parser checks presence, types, syntax, reference resolution, and safe bounds.

Semantic truth, recommendation quality, artifact completion, and person acceptance remain outside parser authority. Structural validity is necessary because downstream owners need dependable form. It is weak evidence about the quality of the judgment inside that form.

10. Consequence moves through distinct standings

The product distinguishes the present judgment, a proposed continuation, human or delegated authorization, the executed effect, acceptance of the result, and renewed ground available to future reasoning.

These states create visible agency. Model prose does not become an invisible command language, and a successful operation does not silently grant epistemic standing to what it wrote.

The interface presents the transition requiring human choice at the moment it matters, while routine mechanical continuation can proceed under grants already accepted.

11. Persistence has an order

A durable operation validates its binding, reads current revisions, performs bounded semantic work, validates the structural return, confirms that its source revisions remain compatible, writes the result and companion state, waits for required settlement, publishes derived views, and only then admits dependent continuation.

Concurrent changes produce a visible collision, reconciliation request, or retry. Last-writer-wins behavior cannot stand in for integration because it cannot explain which meaning survived or why.

12. Reconstruction tests where truth actually lived

After all transient processes terminate, the files recover current artifact revisions, accepted and candidate ground, plan and workflow position, pending recommendations, active assignments, unintegrated returns, lineage, incomplete authorized effects, available next movements, and meaningful defects.

Reload is an epistemic test. If pre-reload appearance and post-reload reconstruction disagree, transient state was carrying hidden authority.

13. Interface regions project one semantic field

Open inquiry, project direction, guided workflows, writing, structural composition, active work, returns, memory, sources, lineage, and correction can appear as distinct product regions. They are not separate minds or independent stores.

Each region projects the same distributed semantic situation at a resolution suited to its cognitive movement. The surface can change while canonical ground and capability ownership remain stable.

14. Provider adapters preserve durable independence

The provider layer translates a stable invocation into model-specific message formats, tool protocols, context limits, streaming, structured output, retry semantics, privacy settings, and model identity evidence.

Portability means the person's artifacts, knowledge, authority, and workflows remain durable when the chosen model changes. It does not promise identical behavior across models; each adapter and capability path requires evaluation.

Local canonical custody also differs from local inference. Composed ground sent to a remote model leaves the device under that provider's technical and contractual conditions.

15. External computation enters through a membrane

An external-agent commission specifies purpose, scope, minimum necessary context, source permissions, allowed tools and effects, evidence contract, time and cost limits, confidentiality, return channel, and integration owner.

The external environment returns a bounded artifact and evidence. Local validation, quarantine where needed, and the acceptance path determine whether the product enters canonical ground.

This membrane lets locally governed intelligence use outside computational scale without exporting its authority along with the task.

The membrane is the product-mechanical realization of the local boundary described in Chapters 16 and 17. The boundary states the limits of purpose, authority, privacy, and consequence; the membrane carries the minimum context and return across that boundary.

16. Failure remains meaningful

Missing sources identify absent ground and limit claims. Provider failure preserves invocation state without inventing an answer. Malformed output remains inspectable where safe but does not enter semantic standing. Parser failure reports structure rather than falsehood. Stale revisions refuse overwrite. Partial writes expose unsettled state and recovery. Orphaned metadata identifies a custody break. Unauthorized effects are prevented and recorded. Reload mismatch prefers file truth and surfaces the reconstruction defect.

Honest failure preserves continuity better than fabricated success.

17. Vertical verification proves the complete movement

Vertical verification is the common public proof method for product capability. Chapter 20 applies it to Atlas change reconciliation and alignment among independent review kinds.

A feature proof follows the person's purpose and gesture, current semantic situation, cognitive movement, provider-visible context, prompt and response contract, durable landing, authority and effect, interface projection, save and collision behavior, renewal, reload reconstruction, and negative-authority evidence.

The proof binds intelligence, interaction, and implementation into one evaluated object. It establishes both what occurred and what remained impossible without authority.

Boundary: machinery carries meaning; it does not originate governing meaning

Capability owners, compilers, parsers, writers, adapters, interfaces, and registries preserve a person's semantic system across execution. Their exactness creates trustworthy custody. Purpose, interpretation, acceptance, and consequential authority remain in the human-governed semantic movement.

18. Failure conditions and evaluation

The principal failure conditions are distinct:

• Universal command bridge: one generic path erases the purpose, sources, contract, effect, and proof owned by each capability.
• Call-site context construction: every feature invents its own relevance rules without a shared semantic owner.
• Machinery in ordinary prompts: queue, parser, schema, or routing concerns displace the language of the work.
• Code-authored conclusion: deterministic logic decides meaning that belongs to situated judgment.
• Parser as epistemic judge: structural validity is treated as evidence of truth or quality.
• Interface as truth: visible state outranks canonical artifacts and reconstructable records.
• Passive semantic watcher: observation creates meaning or consequence without an authorized event.
• Provider-owned durable knowledge: a remote service becomes the only home of purpose, history, or expertise.
• Optimistic persistence: the interface presents settled success before the authoritative writes complete.
• Receipt as outcome quality: proof that an event occurred substitutes for judgment of what the event produced.

Evaluation inspects provider-visible context, machinery leakage, authority fidelity, reconstruction equality, collision safety, cross-provider behavior, injected failure honesty, vertical coherence, proof of disallowed effects, and the person's effort to understand and govern each movement.

Product mechanics succeed when the system can move intelligence through software without losing who meant what, what was authorized, where the result belongs, and whether the same truth returns after everything transient is gone.