Open invitation djat-naoms-20260714 Pathways 1.2.0

A cooperative space where Pathways orchestration meets sovereign memory

Loading…

NAOMS: sovereign substrate

A peer-to-peer personal OS where memory, identity, and group decisions live on chains you own.

Documented protocol surfaces in this bundle

Pathways: the orchestration substrate

The Intelligent Decision Engine (IDE) runs versioned pathway templates as auditable PathwayRuns. This channel is the first collaboration bundle assembled entirely under Pathways spec 1.2.0.

# Document Title Summary

NAOMS domain templates (naoms-pathways/)

    NAOMS UX patterns

      Recommended read order inside the sealed bundle

        Pathways × NAOMS: synergistic cooperation

        How the Pathways ecosystem and the NAOMS community can compose without merging seals or surrendering sovereignty.

        The IDE & Decision Intelligence application

        What this bundle runs today: unique capabilities of the Intelligent Decision Engine and how NAOMS is wired into the reference app.

        Unique capabilities in this build

        How NAOMS is leveraged

        Three anchor integrations: running in the DI fork, encoded as Pathways templates, felt in the NAOMS tab.

        IntegrationMechanismWhat the user feels

        Full directory & asset inventory

        Every major directory in the repository: what it contains, why it exists, and how it connects to Pathways provenance and the NAOMS anchor.

        Running services

        Start everything with start_bundle.sh, the universal landing page polls these ports live.

        Repository tree

        Click a directory to expand its file inventory. Links open the corresponding path on GitHub.

        Three anchor integrations

        How NAOMS is felt in the Decision Intelligence reference application: each integration maps to a Pathways template and a UX pattern.

        Woven projects

        Each card shows how a partner is involved, what the IDE leverages, and how to participate: with clean separation enforced by projects-registry.yaml.

        Weave streams

        Composed siblings linked by hash pointers: never merged seals. The Convergence Repository invariant from Project Weave.

        Participate on your terms

        Reciprocation is welcome but never required. Publish a hash-linked pointer from your channel, bless a template, or run the e2e demo against your own substrate.

        Open a discussion