Skip to content

Ecosystem Overview

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.


Definition: Core protocol implementation and orchestration systems. Mission-critical. Owned/operated by core team.

OrganizationReposProjectsRoleStatus
stratt-hq55GRACE Protocol reference implementation (STRATT)✓ Active
grace-hq17Orchestration intelligence layer (Grace agent)✓ Active
choco-hq4712TimeChain documentation engine (Choco)✓ Active
so1-io357Foundational utilities and integrations (Veritas, shared tools)✓ Active
iris-hq78Sprite 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.


Definition: Production integrations and customer-facing systems. High priority. Regularly updated.

OrganizationReposProjectsFocusStatus
traceo-ai196Execution trace collection and analysis (SPEC-05 traces)✓ Active
sparki-tools23Workflow automation and orchestration tools✓ Active
nestr-tools21Nested structure handling and data transformation✓ Active
cookr-hq2Infrastructure and deployment recipes✓ Active
devarno-cloud23Cloud infrastructure and operations✓ Active
chronicle-hq6Historical 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.


Definition: Early-stage projects and experimental domains. Monitored but not mission-critical. May not be production-ready.

OrganizationReposFocusStatus
clari-tools25Clarity and visualization (pending)🟡 Scaffolded
aphelion-craft25Aphelion craft systems (pending)🟡 Scaffolded
msx-io13Matrix stream exchange (pending)🟡 Scaffolded
skyflow-me25Skyflow data management (pending)🟡 Scaffolded
tektree-io16Tektree knowledge graphs (pending)🟡 Scaffolded
v01t-io24V01t voice integration (pending)🟡 Scaffolded
smo1-io10Smo1 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.


Definition: Legacy, dormant, or specialized projects. Not actively developed. Retained for historical/reference purposes.

OrganizationReposStatus
reactr-dev21🔴 Archive
k41ex5🔴 Archive
featr-io3🔴 Archive
thrustr-io0🔴 Archive

Monitoring: None (historical interest only)

Integration Pattern: No cross-org dependencies. Do not import from these orgs in new work.


Total Organizations: 22
Total Repositories: 356
Total Projects: 44
Total Gists: 207
Last 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 networking

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.0

Resolution: ChocoBridgeResolver in @stratt/graph maps choco:// URIs to HTTP endpoints in choco-hq.

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.yaml across grace-hq and dependent orgs

Each Tier 1-2 org has GitHub Actions workflows:

  • Unit validation — Run STRATT ci on every PR to stratt-hq
  • Build & test — Standard CI for each org
  • Deployment — Docker build → push to registry

The 22-organization ecosystem is governed by 9 councils, each with authority over specific domains:

CouncilDomainAuthorityScope
PathfinderdevLEWIS-06Development, code review, unit authoring
HermesopsRETRO-04Operations, infrastructure, deployment
AthenadocsEDITOR-04Documentation, knowledge, content
BastionsecurityCOMMANDER-05Security policies, compliance, audit
CompassproductCOURSE-05Product direction, feature prioritization
HeraldmarketingCROWN-05Marketing campaigns, brand, messaging
TerradataMANTLE-05Data pipelines, analytics, reporting
Dendriteneuro(Planned)Neuroscience domain, Primer workflows
Primerdomains(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.


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)


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


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.


stratt-hq (Unit registry)
↓ publishes units
grace-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)

  1. Add to ecosystem.yaml in grace-hq with tier, repos, and contact
  2. Import from stratt://shared/* for cross-domain utilities
  3. Use domain-specific units (stratt://yourdom/*)
  4. Submit to council for official adoption (requires gate approval)
  5. Join council meetings (monthly sync for Tier 3, weekly for Tier 2)
  1. Prefer core imports — Import from stratt://core/* and stratt://shared/*
  2. Use stratt:// first — Before creating new shared code
  3. Cross-namespace sparinglychoco:// imports only for contracts, not code
  4. Document integration — Update ecosystem.yaml with dependency relationships
  5. Run ecosystem scan — Monthly check for integration pattern compliance