The canonical document of record for every NeuraWeb entity. Protocols, conformance specifications, technical manuals, partnership agreements, bylaws — versioned, signed, and bridged into the eternal-soul fabric.
What lives here
Eight document families anchor the platform: Protocol, Conformance Specification, Companion Specification, Trust Instrument, Bylaws, Partnership Agreement, Manifest, and Technical Manual. Each family carries its own canonical structure rules — the validation lattice that determines whether a document is a Draft, Working, Signed, Superseded, or Retired instrument under canon.nw.
Documents are authored as ProseMirror JSON inside the shared editor engine (the same engine neuracanvas.nw uses for collaborative authoring). PDFs are derivatives, generated through FirstDrive with watermarking when an instrument is signed. Word and Google Docs round-trips are explicitly outside the canonical pipeline — canon.nw owns its own format because the legal weight of a signed instrument depends on the editor history being intact.
Visibility tiers
Every canon.nw document carries one of five visibility tiers: private (the author alone), connections (the author's connection graph), entity_members (signatories and grant-holders of the owning entity), verified (any verified NeuraWeb identity), and public (open web). Tier is set per document, immutable after signing, and enforced through canon.nw's access lattice — not at the application layer.
Status
Phase 1 — schema, ingest pipeline, and instrument lifecycle — is complete. The corpus browser and document reader (Phase 2 of canon.nw, distinct from Phase 2 of the platform shared UI infrastructure that ships this page) are next. Until those land, canon.nw exposes its inventory through this landing surface.