tcp

Source-of-truth repository for reusable technical capabilities and specifications.

tcp is the technical-capability module of ai4X. It owns the repository boundary for reusable technical capabilities and specifications under cap/. Its public surface exposes the technical-capability boundary, specifications, and supporting governance/docs. Published technical capability roots are added under cap/ when they are admitted to the public portfolio.

tcp follows the ai4X agent-first development model.

Consequences:

• Deterministic checks are handled through metadata, repository gates, and verify.
• Higher-order review, handover, planning, and boundary judgment belong to root ai4X when tcp is evolved inside the ai4X suite context.
• Therefore:
  • doc/usr/* is the direct human-facing documentation surface.
  • doc/agn/* is the agent-facing onboarding and navigation surface.
  • doc/arc/* is module architecture and structure documentation.
  • local adm/dev/* is module-specific governance and normative technical reference.
  • local adm/ops/* is module-specific operations documentation.
• tcp is a domain-owning repository, but ai4X is the governing suite context when tcp is used or evolved inside ai4X.¹
• That matters in practice because:
  • technical capabilities stay explicit and governed instead of hiding inside prompts, wrappers, or runtime glue.
  • specialized agents can reuse shared technical building blocks without polluting ccp or ask.
  • technical guidance remains reusable across public portfolio agents and project-local agents.

For Humans

Copy and paste this prompt to your LLM agent:

Guide me through tcp setup, public technical capability orientation, and first validation by following these sources in order:
1. https://raw.githubusercontent.com/normenmueller/tcp/trunk/doc/agn/user-onboarding.md
2. https://raw.githubusercontent.com/normenmueller/tcp/trunk/doc/usr/primer.md
3. https://raw.githubusercontent.com/normenmueller/tcp/trunk/INSTALL
Then explain what tcp does, show me the public technical capability entry points, and tell me the best next source for my goal.

For Agents

Use this bootstrap prompt when entering tcp from a local checkout or from GitHub:

You are entering the tcp repository for governed work.
If you have a local checkout, use the local equivalents of these sources. Otherwise fetch them directly:
1. https://raw.githubusercontent.com/normenmueller/tcp/trunk/AGENTS.md
2. https://raw.githubusercontent.com/normenmueller/tcp/trunk/CONTRIBUTING.md
3. https://raw.githubusercontent.com/normenmueller/tcp/trunk/INSTALL
4. https://raw.githubusercontent.com/normenmueller/tcp/trunk/doc/agn/maintainer-onboarding.md
5. https://raw.githubusercontent.com/normenmueller/tcp/trunk/doc/agn/source-map.md
If the work is inside the ai4X suite context, also load:
- https://raw.githubusercontent.com/normenmueller/ai4x/trunk/AGENTS.md
- https://raw.githubusercontent.com/normenmueller/ai4x/trunk/adm/dev/protocols/workflow.md
Then summarize the module structure, tell me which local or ai4X protocol applies to the current task, and do not infer workflow from repository layout alone.

License

See LICENSE. © 2026 nemron

Footnotes

1. #eyodf = "eat your own dog food". tcp is maintained with the same agent-first model it helps supply. ↩