Skip to content

Repository structure

The framework repository is 0xPratyaDev7x/kiyo-axiom-framework, formerly kiyo-codejadee-framework; the old path redirects. This map follows the revision the documentation was checked against. Generated caches and other irrelevant artifacts are omitted.

  • Directory.claude-plugin/
    • marketplace.json Claude catalog → ./dist/claude
  • Directory.agents/
    • Directoryplugins/
      • marketplace.json Codex catalog → ./dist/codex/kiyo-axiom-framework
  • Directory.github/
    • Directoryplugin/
      • marketplace.json Copilot catalog → ./dist/copilot/kiyo-axiom-framework
  • Directorysrc/
    • Directorykiyo/ canonical product content (105 Markdown files)
      • KIYO.md compact product entry point
      • README.md authoring notes (developer-only, not packaged)
      • Directoryframework/ Core: authority, context, evidence, DoD, reporting, Memory, controls
        • Directoryengineering/ six engineering standards + selection + standards mapping
          • …
      • Directorygovernance/ governance levels, risk, approval, data, permissions, policy resolution
        • …
      • Directoryagent-security/ AST01–AST10 mapping, trust review, injection, ownership, submodes
        • …
      • Directoryworkflows/ router, adaptive/implement/read-only flows, per-Skill procedures
        • …
      • Directoryprofiles/ .NET, Angular, Python, PostgreSQL + extension contract
        • …
      • Directorytemplates/ 34 neutral templates: init, memory, policies, reports, skill-governance
        • …
      • Directoryskills/ exactly eight SKILL.md entries
        • …
  • Directoryplatforms/
    • Directoryclaude/ plugin.json, marketplace template, resources/activation.md
      • …
    • Directorycodex/ plugin.json, marketplace template, resources/activation.md
      • …
    • Directorycopilot/ plugin.json, resources/activation.md
      • …
  • Directorytools/ developer-only Python packagers, verifier, release rehearsal
    • …
  • Directorytests/
    • Directorystatic/ contract checks + 21 negative fixtures
      • …
    • Directorypackaging/ distribution build and extraction tests
      • …
    • Directoryrelease/ release-candidate regression tests
      • …
    • Directoryaudit/ requirement-ledger audit
      • …
    • Directorylive/ offline audit of recorded host checks
      • …
    • Directorybehavioral/ 48-case evaluation catalog, fixtures, offline helper tests
      • …
  • Directorydocs/
    • Directoryuser/ user guide, Skills, governance, Memory, security, troubleshooting, walkthroughs
      • …
    • Directoryarchitecture/ layout, loading, packaging, naming, distribution build, ADRs
      • …
    • Directorycompatibility/ per-host packages, capabilities, activation, test protocols, live matrix
      • …
    • Directorydeveloper/ maintainer guide
      • …
    • Directoryrelease/ runbooks, owner actions, marketplace draft copy
      • …
    • Directorybuild/ requirements, traceability, progress, decisions, acceptance
      • …
    • Directoryevidence/ dated, redacted check records
      • …
    • Directoryresearch/ sources and standards baseline
      • …
  • Directorydist/ generated packages, development ZIPs, release rehearsals
    • …
  • LICENSE MIT
  • README.md
Directory Responsibility Important files Typically changed by
src/kiyo/ The only authored product specification KIYO.md, framework/bootstrap.md, framework/control-index.md Framework maintainers changing behavior
src/kiyo/skills/ Eight public entries: intent, modes, access contract */SKILL.md (name and description frontmatter only) Maintainers, rarely; keep within budgets
src/kiyo/workflows/ How work proceeds: router, flows, procedures, repair and handoff workflow-router.md, implement-flow.md Maintainers
src/kiyo/templates/ Neutral artifact skeletons users fill in their project reports/*, memory/*, policies/* Maintainers; users fill copies, never these
platforms/ Per-host native manifests and activation adapters */plugin.json, */resources/activation.md Maintainers adapting to host changes
tools/ Build-time packagers, payload verifier, release rehearsal, acceptance audit package_distributions.py, packaging-inputs.json Maintainers; never users
tests/ Static contracts, packaging, release, audit, live-record and behavioral harness static/test_contracts.py Maintainers
docs/ Developer and user documentation, decisions, dated evidence build/DECISIONS.md, compatibility/live-test-matrix.md Maintainers; evidence is append-only in practice
dist/ Generated packages and ZIPs claude/, codex/kiyo-axiom-framework/, copilot/kiyo-axiom-framework/, archives/ Only the packagers
Root catalogs Expose dist/ packages to hosts as custom marketplaces .claude-plugin/, .agents/plugins/, .github/plugin/ Maintainers/publishers
flowchart LR
accTitle: Repository dependency relationships
accDescr: Canonical source and platform overlays feed the packaging tools through an input allowlist. Tools produce dist packages. Tests read source, tools, and dist. Root catalogs point to dist. Docs describe everything but nothing depends on docs at runtime.
SRC[src/kiyo] --> ALLOW[tools/packaging-inputs.json<br/>closed allowlist]
PLAT[platforms/*] --> ALLOW
LIC[LICENSE] --> ALLOW
ALLOW --> PKG[tools/package_*.py]
PKG --> DIST[dist/]
DIST --> CAT[root catalogs]
TESTS[tests/*] -. read .-> SRC
TESTS -. read .-> DIST
TESTS -. import .-> PKG
DOCS[docs/] -. describes .-> SRC

Nothing inside a package references docs/, tools/, tests/, or the source README. The packaging contract makes such a link a build failure.

Item Count How it was established
Canonical product Markdown files 105 Files under src/kiyo/ excluding README.md
Control IDs 68 Unique KIYO-*-NNN IDs in control-index.md, the same set used across src/kiyo/
Templates 34 Files under src/kiyo/templates/
Public Skills 8 Directories under src/kiyo/skills/
Shared files per packaged Skill 97 Files under dist/claude/skills/init/references/kiyo/
Files per package 794 · 795 · 794 Claude · Codex · Copilot package roots