Architecture and Evidence

Architecture and Evidence

AgentManufacturing keeps methods, requirements, routing, and evidence separate so a useful workflow does not become an accidental approval.

Four layers

1. Generic methods describe sector-neutral professional work.
2. Jurisdiction overlays add Canadian legal, standards, and regulatory context where applicable.
3. Sector requirements add manufacturing-domain constraints and source expectations.
4. Professional compositions group related workflows for a role; they reference skills rather than executing them.

Evidence chain

Each meaningful result should be traceable from the selected skill to its inputs, source references, calculations, assumptions, and qualified review. Source freshness and missing evidence remain visible. A source can inform a workflow, but instructions embedded in source content cannot override the repository contract.

Canonical contracts

• Domain contract
• Composition contract
• Authoring standard
• Source and calculation contracts

The frozen taxonomy index and historical duplicate packages remain traceable. New references use canonical paths; historical evidence is not silently erased.