Ecosystem Overview
The 22-Organization Ecosystem
Section titled “The 22-Organization Ecosystem”Grace orchestrates a 22-organization ecosystem spanning 356 repositories, 44 GitHub Projects, and 207 gists. Organizations are classified into 4 tiers based on engagement level and criticality.
For why this ecosystem is organised around verifiable prompt units rather than around services, see Why Verifiable Agentic Prompt Architecture is its own category.
Organization Tiers
Section titled “Organization Tiers”Tier 1: Active Core (5 orgs)
Section titled “Tier 1: Active Core (5 orgs)”Definition: Core protocol implementation and orchestration systems. Mission-critical. Owned/operated by core team.
| Organization | Repos | Projects | Role | Status |
|---|---|---|---|---|
| stratt-hq | 5 | 5 | STRATT Protocol reference implementation | ✓ Active |
| grace-hq | 1 | 7 | Orchestration intelligence layer (Grace agent) | ✓ Active |
| choco-hq | 47 | 12 | TimeChain documentation engine (Choco) | ✓ Active |
| so1-io | 35 | 7 | Foundational utilities and integrations (Veritas, shared tools) | ✓ Active |
| iris-hq | 7 | 8 | Sprite rendering and web publishing (Iris) | ✓ Active |
Monitoring: Daily health checks (FM-01, FM-02, FM-04, FM-09, gate queue, council state)
Integration Pattern: All 5 are deeply coupled. Changes in stratt-hq can affect grace-hq, choco-hq, so1-io, iris-hq in cascade.
Tier 2: Active Products (6 orgs)
Section titled “Tier 2: Active Products (6 orgs)”Definition: Production integrations and customer-facing systems. High priority. Regularly updated.
| Organization | Repos | Projects | Focus | Status |
|---|---|---|---|---|
| traceo-ai | 19 | 6 | Execution trace collection and analysis (SPEC-05 traces) | ✓ Active |
| sparki-tools | 23 | n/a | Workflow automation and orchestration tools | ✓ Active |
| nestr-tools | 21 | n/a | Nested structure handling and data transformation | ✓ Active |
| cookr-hq | 2 | n/a | Infrastructure and deployment recipes | ✓ Active |
| devarno-cloud | 23 | n/a | Cloud infrastructure and operations | ✓ Active |
| chronicle-hq | 6 | n/a | Historical tracking and audit logging | ✓ Active |
Monitoring: Weekly health checks (Tier 2 checks: Primer/Neuro, Choco contracts, cross-namespace resolution)
Integration Pattern: Each integrates with STRATT via specific package dependencies or URI imports. Can be independently deployed/updated.
Tier 3: Scaffolded (7 orgs)
Section titled “Tier 3: Scaffolded (7 orgs)”Definition: Early-stage projects and experimental domains. Monitored but not mission-critical. May not be production-ready.
| Organization | Repos | Focus | Status |
|---|---|---|---|
| clari-tools | 25 | Clarity and visualization (pending) | 🟡 Scaffolded |
| aphelion-craft | 25 | Aphelion craft systems (pending) | 🟡 Scaffolded |
| msx-io | 13 | Matrix stream exchange (pending) | 🟡 Scaffolded |
| skyflow-me | 25 | Skyflow data management (pending) | 🟡 Scaffolded |
| tektree-io | 16 | Tektree knowledge graphs (pending) | 🟡 Scaffolded |
| v01t-io | 24 | V01t voice integration (pending) | 🟡 Scaffolded |
| smo1-io | 10 | Smo1 service mesh (pending) | 🟡 Scaffolded |
Monitoring: Monthly health checks (Tier 3: org reachability, integration pattern compliance)
Integration Pattern: Limited integration with core systems. Mostly standalone with occasional cross-org imports.
Tier 4: Archive / Niche (4 orgs)
Section titled “Tier 4: Archive / Niche (4 orgs)”Definition: Legacy, dormant, or specialized projects. Not actively developed. Retained for historical/reference purposes.
| Organization | Repos | Status |
|---|---|---|
| reactr-dev | 21 | 🔴 Archive |
| k41ex | 5 | 🔴 Archive |
| featr-io | 3 | 🔴 Archive |
| thrustr-io | 0 | 🔴 Archive |
Monitoring: None (historical interest only)
Integration Pattern: No cross-org dependencies. Do not import from these orgs in new work.
Ecosystem Metrics
Section titled “Ecosystem Metrics”Total Organizations: 22Total Repositories: 356Total Projects: 44Total Gists: 207Last Scanned: 2026-04-07
By Tier: Active Core: 5 orgs / 95 repos Active Products: 6 orgs / 114 repos Scaffolded: 7 orgs / 158 repos Archive: 4 orgs / 29 repos
Tech Stack: TypeScript: Main language across core tiers Docker: Containerization standard Git: Version control across all orgs Tailscale: Cross-org mesh networkingCross-Org Integration Patterns
Section titled “Cross-Org Integration Patterns”Pattern 1: STRATT-Centric (Core → Products)
Section titled “Pattern 1: STRATT-Centric (Core → Products)”Tier 2 and 3 organizations integrate with STRATT via:
- Unit imports: Tasks/chains import from
stratt://dev/*,stratt://shared/* - CLI execution: Call STRATT CLI for validation, fingerprinting, gate approval
- Package dependencies: Depend on
@stratt/*packages (@schema, @fingerprint, @graph, @cli)
Example: traceo-ai imports stratt://shared/supply/quality-metrics@1.0.0 for trace scoring.
Pattern 2: Choco Bridge (Cross-Namespace Imports)
Section titled “Pattern 2: Choco Bridge (Cross-Namespace Imports)”STRATT units can import from Choco HQ via choco:// URIs:
imports: - choco://neuro-research/protocol/ethics@3.1.0 - choco://finance/standards/compliance@2.1.0Resolution: ChocoBridgeResolver in @stratt/graph maps choco:// URIs to HTTP endpoints in choco-hq.
Pattern 3: n8n Workflows
Section titled “Pattern 3: n8n Workflows”Automation across orgs via n8n:
- Campaign execution: Grace triggers
CAMPAIGN activate CT-07→ n8n workflow - Trace evaluation: traceo-ai traces → n8n analysis → storage
- Ecosystem sync: Daily sync of
ecosystem.yamlacross grace-hq and dependent orgs
Pattern 4: GitHub Actions CI/CD
Section titled “Pattern 4: GitHub Actions CI/CD”Each Tier 1-2 org has GitHub Actions workflows:
- Unit validation: Run
STRATT cion every PR to stratt-hq - Build & test: Standard CI for each org
- Deployment: Docker build → push to registry
Governance & Councils
Section titled “Governance & Councils”The 22-organization ecosystem is governed by 9 councils, each with authority over specific domains:
| Council | Domain | Authority | Scope |
|---|---|---|---|
| Pathfinder | dev | LEWIS-06 | Development, code review, unit authoring |
| Hermes | ops | RETRO-04 | Operations, infrastructure, deployment |
| Athena | docs | EDITOR-04 | Documentation, knowledge, content |
| Bastion | security | COMMANDER-05 | Security policies, compliance, audit |
| Compass | product | COURSE-05 | Product direction, feature prioritization |
| Herald | marketing | CROWN-05 | Marketing campaigns, brand, messaging |
| Terra | data | MANTLE-05 | Data pipelines, analytics, reporting |
| Dendrite | neuro | (Planned) | Neuroscience domain, Primer workflows |
| Primer | domains | (Planned) | Domain extension, new specialty areas |
Each council has:
- Gate authority agent: Single agent with approval power for frozen transitions
- Protected agents: Agents that cannot be bypassed
- Full agent roster: All agents capable of operating in that domain
See Councils & Agents for full roster.
Namespace Resolution
Section titled “Namespace Resolution”stratt:// (STRATT Units)
Section titled “stratt:// (STRATT Units)”Format: stratt://{domain}/{type}/{slug}@{version}
Resolution: Local filesystem → ~/code/workspace/stratt-hq/packages/units/{domain}/{type}/
Domains: 15 total (dev, ops, docs, shared, neuro, finance, nutrition, legal, film, artist, security, product, data, marketing, core)
Types: 5 total (role, rule, task, chain, supply)
choco:// (Choco HQ Contracts)
Section titled “choco:// (Choco HQ Contracts)”Format: choco://{namespace}/{path}@{version}
Resolution: HTTP endpoint in choco-hq → ~/code/workspace/choco-hq/{namespace}/{path}/
Namespaces: Non-core domains (neuro, finance, nutrition, legal, film, etc.)
Resolver: ChocoBridgeResolver in @stratt/graph/src/choco-resolver.ts
grace:// (Future)
Section titled “grace:// (Future)”Format: grace://{scope}/{path}@{version}
Status: Planned (not yet implemented)
Scope: Architecture artifacts, automation, configuration from grace-hq
See Namespaces & URIs for full technical specification.
Cross-Org Data Flow
Section titled “Cross-Org Data Flow”stratt-hq (Unit registry) ↓ publishes unitsgrace-hq (Orchestration) ├← imports units from stratt-hq ├→ routes to Tier 2-3 orgs ├← monitors health (9 councils) └→ coordinates campaigns (n8n, Herald council)
choco-hq (Documentation) ├← imports from stratt-hq (ChocoBridgeResolver) ├→ serves via choco:// URIs └→ hosts Primer (domain extension)
Tier 2-3 Orgs ├← consume stratt:// units ├← consume choco:// contracts ├→ publish execution traces (traceo-ai) └→ report operational state (devarno-cloud, chronicle-hq)Integration Best Practices
Section titled “Integration Best Practices”For New Tier 2/3 Organizations
Section titled “For New Tier 2/3 Organizations”- Add to
ecosystem.yamlin grace-hq with tier, repos, and contact - Import from stratt://shared/* for cross-domain utilities
- Use domain-specific units (stratt://yourdom/*)
- Submit to council for official adoption (requires gate approval)
- Join council meetings (monthly sync for Tier 3, weekly for Tier 2)
For Cross-Org Dependencies
Section titled “For Cross-Org Dependencies”- Prefer core imports: Import from
stratt://core/*andstratt://shared/* - Use stratt:// first: Before creating new shared code
- Cross-namespace sparingly:
choco://imports only for contracts, not code - Document integration: Update
ecosystem.yamlwith dependency relationships - Run ecosystem scan: Monthly check for integration pattern compliance
Next Steps
Section titled “Next Steps”- Councils & Agents: 9 councils and 41 agent designations
- Namespaces & URIs: URI scheme technical specification
- Assistant: Grace orchestration overview
- Protocol:
SPEC-03dependency graph