Complete AMOS product architecture specifications

[EltonChang1]

What changed

• Expanded the AMOS design proposal into a complete 31-page product architecture and end-to-end implementation guide.
• Added normative first-release decisions and embedded Specifications A–F for transactions, concurrency, publication, persistence, context, connectors, workers, verification, claims, review, invalidation, and replay.
• Added 14 concrete contract examples and eight temporal sequence diagrams covering normal execution, revocation, repair, human review, source changes, worker recovery, publication, and replay.
• Defined the alpha capability boundary, deferred unsafe capabilities explicitly, and strengthened startup phasing, security, tenancy, operations, testing, and qualification gates.
• Updated the README description while preserving the exact paper title and the repository's two-PDF structure.

Why

The previous architecture established the complete subsystem map but still required implementers to invent several low-level contracts. This revision freezes the first-release decisions needed to build AMOS end to end under harsh engineering review.

Impact

A startup team can now use the design proposal as both the product architecture and the implementation contract for a phased build, paid pilot, and later controlled autonomy.

Validation

• 85 tests passed
• LaTeX build completed without warnings, overfull boxes, or undefined references
• All 31 pages rendered and visually inspected
• Structural audit confirmed all six specifications, 14 listings, nine figures, exact PDF metadata, and no empty pages
• Exactly two PDFs remain in papers/
• Removed cover text and the duplicated title remain absent

[Copilot]

Pull request overview

Expands the AMOS design proposal into a complete product architecture and implementation contract, and updates the repository’s top-level README to reflect the strengthened specification scope.

Changes:

• Updated README wording to emphasize concrete first-release contracts and implementation guidance.
• Expanded papers/design_proposal.tex with normative language, additional architecture constraints, and Specifications A–F (contracts, diagrams, and examples).

Reviewed changes

Copilot reviewed 2 out of 3 changed files in this pull request and generated 1 comment.

File	Description
README.md	Updates the design proposal description to reflect expanded implementation-contract coverage.
papers/design_proposal.tex	Adds normative contract language, additional runtime/tenancy/publication requirements, and appended Specifications A–F with examples/diagrams.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.