---
id: capability.infotech.repo-template
name: Coulomb Repository Template
summary: Bootstrap new git repositories with agent instructions, registry scaffold, and State Hub onboarding conventions.
owner: repo-seed
status: draft
domain: infotech
tags:
  - template
  - bootstrap
  - state-hub
  - onboarding

maturity:
  discovery:
    current: D3
    target: D5
    confidence: medium
    rationale: >
      Template purpose, consumer guide, and validation checklist are documented.
      Scope boundaries are explicit in SCOPE.md.
  availability:
    current: A3
    target: A4
    confidence: medium
    rationale: >
      Consumers clone or copy repo-seed and run statehub register. Template
      files are markdown/git artifacts without a hosted provisioning API.

external_evidence:
  completeness:
    level: C2
    confidence: medium
    basis: scope_vs_intent_and_consumer_expectations
    satisfied_expectations:
      - agent instruction scaffold (AGENTS.md, CLAUDE.md, .claude/rules/)
      - registry directory scaffold
      - statehub register consumer documentation
      - template validation checklist for bootstrap verification
      - bootstrap workplan pattern (WP-0001)
    broken_expectations: []
    out_of_scope_expectations:
      - automated repo creation on Gitea
      - runtime application code generation
  reliability:
    level: R2
    confidence: medium
    basis: consumer_quality_signals
    known_reliability_risks:
      - register output evolves with state-hub releases; checklist must be revalidated
      - LLM inference path depends on llm-connect availability

discovery:
  intent: >
    Give new Coulomb repositories a consistent starting point for agent
    coordination, capability registry growth, and State Hub workplan tracking.
  includes:
    - git template files for agent instructions and registry scaffold
    - documentation for statehub register usage
    - consumer validation checklist
    - bootstrap workplan convention
  excludes:
    - application runtime implementation
    - owning downstream project code
  assumptions:
    - consumers have access to state-hub CLI and API
    - workplans remain canonical in repo files (ADR-001)
  use_cases: []
  research_memos:
    - docs/statehub-register.md
    - docs/template-validation-checklist.md

availability:
  current_level: A3
  target_level: A4
  current_artifacts:
    - README.md
    - AGENTS.md
    - CLAUDE.md
    - .claude/rules/
    - registry/
    - docs/statehub-register.md
    - docs/template-validation-checklist.md
  consumption_modes:
    - git clone
    - informational

relations:
  depends_on:
    - capability.statehub.workstream-coordinate
  supports: []
  related_to:
    - capability.registry.register

evidence:
  documentation:
    - docs/statehub-register.md
    - docs/template-validation-checklist.md
    - SCOPE.md
  tests: []

consumer_guidance:
  recommended_for:
    - bootstrapping new Coulomb domain repositories
    - standardizing agent onboarding and workplan conventions
  not_recommended_for:
    - repos that already have mature agent instructions and hub registration
    - application templates with heavy code generation requirements
  known_limitations:
    - register must be run separately after cloning
    - fix-consistency requires operator access to state-hub checkout
---

# Coulomb Repository Template

`repo-seed` is the canonical git template for new Coulomb repositories. Clone it,
run `statehub register`, complete the bootstrap workplan, and sync with
`make fix-consistency`.

See `docs/statehub-register.md` for the consumer workflow and
`docs/template-validation-checklist.md` for verification steps.