Portfolio
A one-line index of every clan / project named as an example in the Canopy methodology docs. Exists so primitive docs can reference "Howler" without restating what Howler is. Source: the v7.0 validation audit (
docs/methodology/validation/VALIDATION.md).
These are real working clans, not hypotheticals. Naming them is a credibility moat: the method emerged from these portfolios, not from a whiteboard.
Clans
| Name | One-line context | Used in |
|---|---|---|
| Howler | Voice-AI telephony bridge between Twilio/Telnyx and Anthropic; carries bridge + router + conductor as a single cross-cutting subsystem. | INITIATIVES.md, METHOD.md |
| Cortex | LLM gateway / model router with plugin system. The reference example for plugin-style Initiatives. | INITIATIVES.md, CROSS-CLAN.md |
| Cortex Nexus | The always-on Alpha process for Cortex. Cortex itself ships through Nexus continuously. Canonical LivingProcess example. | LIVING-PROCESS.md, METHOD.md |
| Persona | User-identity and context provider. Depends on Cortex API keys — canonical CrossClanDependency consumer. | CROSS-CLAN.md |
| ROM Web | Web surface of the ROM product line. Paired with ROM Mobile via back-port CrossClanDependency. | CROSS-CLAN.md, BUGS.md |
| ROM Mobile | Mobile surface of the ROM product line. Issue diagnostic vocabulary (reproduced / isolated) emerged from ROM Mobile's debugging reality. | CROSS-CLAN.md, BUGS.md |
| Canopy | This project. The methodology + the platform + the CLI. Self-references appear in METHOD.md where Canopy itself models a primitive. | METHOD.md, all primitive docs |
| Jungle Obsidian | Registry / knowledge clan inside the Jungle council. Always-on Alpha; LivingProcess. | LIVING-PROCESS.md |
| Jungle Nexus | Messaging / routing clan inside the Jungle council. Always-on Alpha; LivingProcess. | LIVING-PROCESS.md |
| Jungle Webmaster | The Webmaster Council-tier agent. Always-on; LivingProcess. | LIVING-PROCESS.md |
| MOIMF | Governance / Alpha-Verdict clan. Carries a mandatory browser-smoke pre-deploy gate (Invariant). | INVARIANTS.md |
| DCD | Healthcare clan. Carries HIPAA as a standing Invariant across every Outcome. | INVARIANTS.md |
| Scribe | Content clan. Carries a no-hardcoded-hex Invariant — brand-color enforcement at lint time. | INVARIANTS.md |
| Trellis | Civic / township platform. Carries a statute-grounding Invariant; also uses Milestone.calendar_anchor for legally-mandated dates. |
INVARIANTS.md, OUTCOMES.md |
| Barrel | Audit-trail clan. Audit-trail required as a standing Invariant. | INVARIANTS.md |
| TestKillerProject | SOC 2 / claims-processing clan. Standing SOC 2 Invariant. | INVARIANTS.md |
| Plain | Analyzer-pass program. Retroactive-Outcome example (is_retroactive: true backfill pattern). |
OUTCOMES.md, INITIATIVES.md |
| FirstContactGaming | Mobile gaming clan. Uses Milestone.calendar_anchor for App Store submission gates. |
OUTCOMES.md |
| JARVIS | Registered clan with a running workload at emailme/; consumes 9.45M Cortex tokens/day. LivingProcess example. | LIVING-PROCESS.md, CROSS-CLAN.md |
If you add an example to a primitive doc that names a new clan, add a row here in the same commit. PORTFOLIO.md exists to keep the per-doc cognitive load down — primitive docs assume the reader can look up "Howler" without disrupting flow.