Publish DreamLoops and Capsules origin record

[BrandonDucar]

What changed

• Repositioned the repository landing page so DreamLoops, Capsules, receipts, and lineage are presented as one architecture.
• Added CAPSULES.md as a dedicated discovery and education gateway without splitting the canonical specification into a second repository.
• Added a public origin paper documenting definitions, the architecture, the ZOL proof case, the novelty boundary, and the dated June–July 2026 chronology.
• Linked the canonical DreamLoop and Capsule specifications, schema, examples, and origin materials from the README.

Why

The repository already contained the working Capsule and DreamLoop specifications and runtime, but the public landing page did not make Capsules equally visible or clearly state the combined architecture and dated authorship record.

This PR preserves the existing dreamloops repository and its commit history while making the supported priority statement explicit:

By July 14, 2026, DreamNet had publicly specified and implemented DreamLoops and Capsules as a unified system for portable, bounded, inheritable, receipt-backed agent intelligence.

The paper deliberately distinguishes this specific integrated architecture from unsupported claims that DreamNet invented every individual ingredient such as loops, modules, memory, hashing, or workflow systems.

Impact

Documentation only. No runtime, schema, signer, wallet, permission, deployment, or production behavior changes.

Validation

• Compared the branch against main: three documentation files changed, zero runtime files changed.
• Confirmed the linked Capsule schema exists on the branch.
• Preserved the canonical specs and existing public history in the original repository.

After merge

Create a tagged documentation release so the origin paper, specifications, and changelog are captured together at a stable release reference.