Satoshium Repo Map
This page groups the major Satoshium repositories by architectural and service-support role. It is not a complete inventory of every repository in the workspace. It is a public map of the repositories that most directly support Satoshium’s public service surfaces, knowledge layer, trust and verification layer, interfaces, documentation, and operational continuity.
This map reflects the active public architecture of Satoshium. Internal provenance repositories from earlier build phases are not shown here.
🧱 How to Read the Repo Map
The repo map mirrors the broader platform structure. Some repositories define stable foundations. Some support public services, documentation, review workflows, verification records, and controlled evaluation surfaces. Others are internal or supporting. Together they form the working repository ecosystem behind Satoshium.
🛠️ Public Service Repository Alignment
The strongest current SOU-facing public service surfaces are supported by repositories and documentation patterns that connect software behavior, public pages, service descriptions, structured outputs, and build continuity.
- Aegis: AI agent inspection and lifecycle verification service surfaces.
- Agent Governance: governance evaluation, policy review, decision records, and exportable artifacts.
- Verification Ledger: tamper-evident verification records, SHA-256 references, ledger reports, and integrity validation workflows.
- Documentation and Updates: public continuity records connecting service refinements, architecture pages, build history, and supporting evidence.
These repository and page relationships support public-facing software-service continuity without claiming custody, autonomous enforcement, production execution authority, or ledger mutation.
🗺️ Platform Alignment
- Architecture: explains the layered model of the platform.
- Systems: documents the functional software systems.
- Build: explains the engineering direction over time.
- Registry: provides canonical public identifiers for system-level components.
🎯 Repo Map Purpose
- Show where the most important repos fit in the architecture
- Separate stable foundations from experiments and public interfaces
- Clarify how public pages relate to underlying project repositories
- Support long-term traceability, public service continuity, and documentation review as the ecosystem grows
📜 Canon & Specifications Layer
- satoshium-canon — constitutional truth layer for platform definitions, claims, doctrine, and source-of-truth concepts
- satoshium-specs — structured specifications for agents, models, lifecycle logic, standards, and platform definitions
- satoshium-governance — governance doctrine, policy thinking, and coordination concepts supporting public governance evaluation workflows
These repositories move slowly. They define the stable conceptual structure that public services, interfaces, documentation, and agents should inherit rather than invent on the fly.
📚 Knowledge Engine & Documentation Layer
- satoshium-glossary — canonical terminology base for the emerging Knowledge Engine
- glossary-builder — interactive interface for creating, reviewing, and exploring platform terminology
- satoshium-docs — structured documentation, references, and supporting technical materials
- satoshium-journal — development record, milestone logs, and historical traceability of the build
- satoshium-master-timeline — long-horizon progress tracking and sequencing of major platform work
Shared language and documented history are part of the platform itself. This layer supports consistency, traceability, and human + AI reasoning, service documentation, and review workflows.
🔧 Public Services & Operational Tooling Layer
- Aegis Service surfaces — AI agent inspection, lifecycle verification, structured readiness outputs, and service-boundary review
- Agent Governance Tool — ruleset evaluation, governance review, JSON exports, TXT reports, execution receipts, and cryptographic decision records
- Verification Ledger Tool — tamper-evident verification records, SHA-256 references, exportable audit artifacts, and integrity validation
- Services overview — public description layer connecting service pages, tools, documentation, and user-accessible interfaces
This layer represents the strongest current operational evidence of Satoshium as a public-facing software and service ecosystem.
🛡️ Trust, Safety & Verification Layer
- satoshium-trust — trust primitives, verification logic, and patterns for governed intelligence systems and verification workflows
- satoshium-safety — safety doctrine, constraints, and protective design patterns
- satoshium-aegis — public-facing direction for AI agent inspection, lifecycle verification, and service-boundary review concepts
- satoshium-certifier — verification and certification logic for assessing system or agent readiness
- satoshium-registry — registry patterns, identities, and structured indexing concepts for platform components and service documentation
This layer exists to prevent Satoshium from becoming intelligence without discipline. Trust, verification, and safety are architectural requirements that support public inspection, governance, and verification services.
🤖 Intelligence, Core Logic & Agent Layer
- satoshium-core — shared platform logic, reusable utilities, and core patterns used across Satoshium systems
- satoshium-interface — interface direction for interacting with Satoshium systems, knowledge, and research flows
- satoshium-agent-lab — sandbox for testing different agent forms, internal workflows, and architectural ideas
- satoshium-agents — longer-term home for aligned agent systems as the architecture matures
- satoshium-curator — canon-aware curation, structured updates, and knowledge maintenance logic
- satoshium-echobot / satoshium-saynobot — project-specific agent experiments and applied behavioral concepts
Agents are not the starting point of Satoshium. They emerge from the knowledge, trust, governance, and verification layers once the foundation is strong enough to support them.
🧪 Evaluation, Labs & Scenario Layer
- satoshium-labs / public Labs environment — supporting public layer for controlled evaluation and interactive system exploration
- satoshium-scenarios — scenario-based modules for testing how systems behave in structured situations
- satoshium-simulations — evaluation-oriented repo space for interactive or model-driven testing
- satoshium-demos — smaller public prototypes, interfaces, and testable review demonstrations
- satoshium-future-uses — applied scenario thinking and long-range use cases for the broader Satoshium architecture
This is the controlled evaluation track of the ecosystem. Evaluation surfaces help turn abstract concepts into testable ideas before they are treated as stable platform capabilities.
📡 Signal & Coordination Layer
- satoshium-signal — infrastructure signal routing surface for proposals, coordination entries, and long-horizon platform inputs
- signal-boards — structured intake interface for infrastructure signals across Bitcoin, AI alignment, and Satoshium architecture
- sovereign-signal — scenario-driven signaling environment for exploring strategic coordination pathways
The Signal Layer provides structured visibility and coordination pathways across the decentralized intelligence stack. It connects proposals, simulations, governance surfaces, and service interactions before they become formal platform systems.
🌐 Public Surface & Experience Layer
- satoshium-progress — public build log, architecture portal, update record, and documentation gateway
- satoshium-site — main public narrative site and broader public-facing platform story
- satoshium-ui — user interface direction, visual systems, and design-alignment work
- satoshium-hub — coordination or entry-point layer for platform navigation
- satoshium-academy — educational surface for learning-oriented materials and structured onboarding
These repositories shape how the platform is encountered publicly. They do not replace the deeper layers beneath them; they expose services, documentation, and public interfaces carefully.
🧰 Supporting Infrastructure & Internal Utility Repos
- satoshium-data — data structures, supporting assets, or structured platform inputs
- satoshium-devtools — internal tooling and developer support workflows
- satoshium-utils — small utilities and support functions used across the workspace
- satoshium-internal — internal working documents, coordination notes, and private support materials
- satoshium-drafts — draft-stage documents, work-in-progress assets, and early content staging
- satoshium-template — repo template and structural baseline for future aligned repositories
Not every repo is a public system. Some exist to keep the workspace consistent, maintainable, and capable of supporting public services, documentation, and long-horizon platform growth.
🎬 Media, Storytelling & Narrative Layer
- satoshium-chronicles — narrative, story, or long-form historical framing for the project
- satoshium-glyphs — symbolic, visual, or design-oriented language for Satoshium concepts
- satoshium-founder / satoshium-mirror — founder-facing or reflective spaces that may support long-horizon project clarity
Satoshium is not only engineered. It is also interpreted, explained, and made understandable over time.
🧭 Reading the Workspace as a Whole
The full Satoshium workspace is larger than the public repo map shown here. The public map focuses on repositories that most clearly support the platform's constitutional layer, Knowledge Engine, trust systems, intelligence systems, public services, controlled evaluation environments, and public-facing documentation.
As the ecosystem grows, the most system-critical repositories should continue to align with the Architecture page, the Build page, the Services page, and the public Registry so that the platform remains understandable rather than merely expansive.