# Technology profile repository coverage review
### Delivery record and implementation boundaries

[![AI SAFE²](https://img.shields.io/badge/AI_SAFE%C2%B2-v3.1-F6921E?style=flat-square)](../README.md)
[![Review](https://img.shields.io/badge/Docs-Repository_Review-820F1A?style=flat-square)](./TECHNOLOGY-PROFILE-REPO-REVIEW.md)

[Framework Home](../README.md) | [Cross-Pillar Governance](../00-cross-pillar/README.md) | [AISM](README.md) | [NEXUS](../NEXUS/README.md) | [Technology Profile](./TECHNOLOGY-CONTRIBUTION-PROFILE.md)

---

**Documentation updated:** 2026-10-02. TCP and Evidence Assurance v1.0 are CSI
assessment methods for use and feedback. All AISM pages include a dated change
summary and link the [practical assessment guide](ASSESSMENT-GUIDE.md).
Release announcements are prepared outside the repository for owner publication.

## Canonical-home update (2026-10-13)

The complete TCP, Evidence Assurance, Technology Card, validation, incident-review,
and repository-coverage documents now live under `AISM/`. Current repository links
and machine-discovery pointers use these paths. The
[technology evidence request](./TECHNOLOGY-EVIDENCE-REQUEST.md) supports provider
and internal-owner intake before claim review. Earlier pinned revisions preserve
the original paths; unpinned links to the former `docs/` files must be updated.
The record below describes the original introduction; this relocation changes
no method version, rubric, organizational formula, or runtime contract.

## Outcome and acceptance boundary

The current full name is **AI Sovereign Maturity (AISM) Model**, shortened to
AISM or AISM Model. Current headings, root navigation, scoring/assessment prose,
and naming guidance use this expansion. Historical submission wording and asset
filenames remain intact with a current-name pointer; the Sovereignty Score and
Sovereignty Matrix retain their distinct names. This is an editorial naming
change with no scoring, schema, command, or path migration.

This method separates organizational AISM maturity, scoped artifact contribution,
and claim-level assurance throughout repository guidance. Acceptance requires a
central review method, reusable card, all nine supplied example dispositions,
canonical control references, actionable validation/incident practices, root
navigation, machine discovery, and clear compatibility/implementation limits.

Base: `e66182e93bef1debe61c2cc17f089c60d16829a9`, fetched from the repository's
default `main` branch on October 2, 2026. Work is isolated on
`docs/technology-contribution-profile`. The PR head commit is the exact revision
under review; later changes require affected checks to be rerun.

Before: organizational methodology, CLI numeric E grades, and Challenge Lab C
levels existed, but no dedicated artifact contribution/card/assurance-v1.0 review
entry point existed. After: the linked method names each instrument and preserves
their distinct meanings. This is a document/path comparison, not an experiment
demonstrating improved deployed security.

## Coverage review

| Repository surface | Changes or reviewed disposition |
|---|---|
| [Root README](../README.md), [quickstart](../QUICKSTART_5_MIN.md) | New three-instrument summary, method/card/examples links, score interpretation |
| [Agent entry point](../AGENTS.md), [manifest](../ai-safe2.manifest.json) | Discovery pointers, method/implementation status, explicit separation from organizational maturity and CLI grades |
| [Shield](../01-sanitize-isolate/README.md) | Actual interception/judgment/actuation boundary, composed paths, side effects |
| [Ledger](../02-audit-inventory/README.md) | Evidence origin, protected records, reconstruction, retention and notification ownership |
| [Circuit Breaker](../03-fail-safe-recovery/README.md) | Actuation/stopping authority, direct/descendant bypass, outage and revocation tests |
| [Command Center](../04-engage-monitor/README.md) | Probabilistic judgments, forged process evidence, accountable notification |
| [Learning Engine](../05-evolve-educate/README.md) | Paired testing, benchmark limits, learned-policy integrity and owned regressions |
| [Cross-Pillar Governance](../00-cross-pillar/README.md) | Applicable CP.5 profile/plane, CP.6 feedback, CP.10 rights/stopping authority |
| [AISM README](README.md), [methodology](AISM-Scoring-Matrix-Methodology.md), [assessment](AISM-Self-Assessment-Tool.md), [maturity ladder](maturity-model.md) | Organizational subject retained; scoped technology evidence cannot assign organizational cells or levels automatically |
| [Crosswalk](AISM-Compliance-Crosswalk.md), [threat matrix](agent-threat-control-matrix.md), [control stack](control-stack.md), [operational loop](operational-loop.md) | Procurement rule, evidence effect vocabulary, boundary tests, owned incident/policy-learning intake |
| [AISM strategic architecture](strategic-architecture.md), [sovereignty matrix](sovereignty-matrix.md) | Reviewed organizational governance/control/autonomy context; no axis, architecture, or formula change needed |
| [NEXUS](../NEXUS/README.md), [Gateway](../gateway/README.md) | Same claim discipline for first-party implementations; actual tested version and plane; native risk routing separate |
| [Scanner](../scanner/README.md), [Skills](../skills/README.md), [MCP server](../skills/mcp/README.md) | Static/inspection evidence separate from runtime enforcement; native verdict/score semantics retained |
| [CLI](../safe2/README.md), [scope guide](../docs/ASSESSMENT-SCOPE.md), [readiness](../safe2/docs/RELEASE-READINESS.md) | No TCP command or payload; existing intake/unscored cells, E weights/caps/categories, and human release authority retained |
| [Dashboard](../dashboard/README.md) | Proposed future presentation boundary; no new TCP view or relabeling of current scores |
| [Examples index](../examples/README.md), [research index](../research/README.md) | Method/card pointers, nine-example review; no runnable integration added or generated table hand-edited |
| [Challenge Lab](../challenges/README.md), [harness design](../safe2/docs/CHALLENGE-HARNESS-DESIGN.md), [CLI guide](../safe2/docs/CHALLENGE-CLI.md) | C scale distinct, new test candidates explicit; frozen Challenge 001 and current executable scope untouched |
| [Contribution guidance](../CONTRIBUTING.md), [PR template](../.github/PULL_REQUEST_TEMPLATE.md) | Claim/control/boundary evidence requirements and separate proposal/result states |
| [Evolution](../EVOLUTION.md), [CLI roadmap](../safe2/docs/CLI-ROADMAP-TO-1.0.md), [brief triage](../safe2/docs/SECURITY-BRIEF-2026-09-13-TRIAGE.md), [UX standard](../docs/REPOSITORY-UX-STANDARD.md) | Assessment methods recorded; runtime work/version migration deferred; navigation and terminology rules linked |
| Core/profile datasets, NEXUS schemas, scanner rules, CLI schemas/scoring, dashboard generated data | Reviewed relevant IDs, versions, counts, discovery, grade/cap semantics; no contract change required for Markdown review instruments |
| Historical notes, release notes, published assets | Kept as original records; new source-reviewed guidance is discoverable from current indexes rather than rewriting historical evidence |

## Delivered documents and deferred work

- [Contribution methodology](./TECHNOLOGY-CONTRIBUTION-PROFILE.md).
- [Evidence Assurance v1.0](./EVIDENCE-ASSURANCE.md), separate from current CLI grades.
- [Reusable Technology Card](./templates/TECHNOLOGY-CARD.md).
- [Validation practices](./TECHNOLOGY-VALIDATION.md) and [incident evidence](./INCIDENT-EVIDENCE.md).
- [Nine source-attributed examples and ownership backlog](../research/technology-contribution-examples.md).

The actual kernel/runtime integrations, new benchmark experiments, policy-memory
governor, production evidence collection, TCP machine schema/CLI/dashboard, and
grade translation are deferred implementation proposals with acceptance evidence
listed in the backlog. No live offensive evaluation or external notification was
performed. No organization or candidate was certified or assigned a maturity level.

## Risks, compatibility, and ownership

The principal risk is readers converting a capability, source claim, or E rating
into maturity or certification. The documents counter that through explicit
subject, effect, boundary, assurance rubric/version, provenance, independent
review status, and unassessed states. Producer claims remain attributed; the
notification count remains unverified. Examples' supplied numeric ratings are
not promoted without their underlying evidence.

Framework controls remain 161; CP.5.MCP remains 19 profile controls; UAS remains
27 profile requirements. Existing versions, formulas, numeric E weights,
verification caps, schemas, and frozen challenge artifacts remain unchanged.
Manifest additions are discovery-only, not schema catalog or executable commands.

CSI maintains the v1.0 assessment methods and welcomes evidence-based feedback;
deployment/incident owners make adoption, risk, retention, and notification
decisions. No decision authority is delegated by this change. Rollback is a revert
of the documentation/discovery commit; no runtime state or data migration exists.
Independent review and hosted CI status belong to the PR, not to a fabricated
assurance score for this self-review.

## Verification

Run from the repository root:

```bash
python scripts/check_repo_ux.py
python scripts/generate_examples_table.py --check
python scripts/check_agent_manifest.py
python -m pytest tests/ scanner/tests/ -q
```

Check added local Markdown destinations/anchors and canonical control IDs as
part of document review. Hosted Linux and supported Python-matrix checks remain
separate from local Windows results. The PR records actual outcomes and any
baseline or environment limitations at the tested revision.

---

[Technology Profile](./TECHNOLOGY-CONTRIBUTION-PROFILE.md) | [Evidence Assurance](./EVIDENCE-ASSURANCE.md) | [Examples](../research/technology-contribution-examples.md)

*AI SAFE² v3.1 · [Cyber Strategy Institute](https://cyberstrategyinstitute.com/ai-safe2/)*
