intentdna 1.7.4 → 1.8.0

package/.claude-plugin/marketplace.json

@@ -9,7 +9,7 @@
     {
       "name": "intentdna",
       "description": "Declarative policy layer for AI agent behavior with plugin-managed hook runtime for Claude Code.",
-      "version": "1.7.4",
+      "version": "1.8.0",
       "author": {
         "name": "Samuel"
       },
@@ -25,5 +25,5 @@
       ]
     }
   ],
-  "version": "1.7.4"
+  "version": "1.8.0"
 }

package/.claude-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "intentdna",
-  "version": "1.7.4",
+  "version": "1.8.0",
   "description": "Declarative policy layer for AI agent behavior",
   "author": {
     "name": "Samuel"

package/LICENSE

@@ -0,0 +1,201 @@
+Apache License
+Version 2.0, January 2004
+http://www.apache.org/licenses/
+
+TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+1. Definitions.
+
+"License" shall mean the terms and conditions for use, reproduction,
+and distribution as defined by Sections 1 through 9 of this document.
+
+"Licensor" shall mean the copyright owner or entity authorized by
+the copyright owner that is granting the License.
+
+"Legal Entity" shall mean the union of the acting entity and all
+other entities that control, are controlled by, or are under common
+control with that entity. For the purposes of this definition,
+"control" means (i) the power, direct or indirect, to cause the
+direction or management of such entity, whether by contract or
+otherwise, or (ii) ownership of fifty percent (50%) or more of the
+outstanding shares, or (iii) beneficial ownership of such entity.
+
+"You" (or "Your") shall mean an individual or Legal Entity
+exercising permissions granted by this License.
+
+"Source" form shall mean the preferred form for making modifications,
+including but not limited to software source code, documentation
+source, and configuration files.
+
+"Object" form shall mean any form resulting from mechanical
+transformation or translation of a Source form, including but
+not limited to compiled object code, generated documentation,
+and conversions to other media types.
+
+"Work" shall mean the work of authorship, whether in Source or
+Object form, made available under the License, as indicated by a
+copyright notice that is included in or attached to the work
+(an example is provided in the Appendix below).
+
+"Derivative Works" shall mean any work, whether in Source or Object
+form, that is based on (or derived from) the Work and for which the
+editorial revisions, annotations, elaborations, or other modifications
+represent, as a whole, an original work of authorship. For the purposes
+of this License, Derivative Works shall not include works that remain
+separable from, or merely link (or bind by name) to the interfaces of,
+the Work and Derivative Works thereof.
+
+"Contribution" shall mean any work of authorship, including
+the original version of the Work and any modifications or additions
+to that Work or Derivative Works thereof, that is intentionally
+submitted to Licensor for inclusion in the Work by the copyright owner
+or by an individual or Legal Entity authorized to submit on behalf of
+the copyright owner. For the purposes of this definition, "submitted"
+means any form of electronic, verbal, or written communication sent
+to the Licensor or its representatives, including but not limited to
+communication on electronic mailing lists, source code control systems,
+and issue tracking systems that are managed by, or on behalf of, the
+Licensor for the purpose of discussing and improving the Work, but
+excluding communication that is conspicuously marked or otherwise
+designated in writing by the copyright owner as "Not a Contribution."
+
+"Contributor" shall mean Licensor and any individual or Legal Entity
+on behalf of whom a Contribution has been received by Licensor and
+subsequently incorporated within the Work.
+
+2. Grant of Copyright License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+copyright license to reproduce, prepare Derivative Works of,
+publicly display, publicly perform, sublicense, and distribute the
+Work and such Derivative Works in Source or Object form.
+
+3. Grant of Patent License. Subject to the terms and conditions of
+this License, each Contributor hereby grants to You a perpetual,
+worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+(except as stated in this section) patent license to make, have made,
+use, offer to sell, sell, import, and otherwise transfer the Work,
+where such license applies only to those patent claims licensable
+by such Contributor that are necessarily infringed by their
+Contribution(s) alone or by combination of their Contribution(s)
+with the Work to which such Contribution(s) was submitted. If You
+institute patent litigation against any entity (including a
+cross-claim or counterclaim in a lawsuit) alleging that the Work
+or a Contribution incorporated within the Work constitutes direct
+or contributory patent infringement, then any patent licenses
+granted to You under this License for that Work shall terminate
+as of the date such litigation is filed.
+
+4. Redistribution. You may reproduce and distribute copies of the
+Work or Derivative Works thereof in any medium, with or without
+modifications, and in Source or Object form, provided that You
+meet the following conditions:
+
+(a) You must give any other recipients of the Work or
+Derivative Works a copy of this License; and
+
+(b) You must cause any modified files to carry prominent notices
+stating that You changed the files; and
+
+(c) You must retain, in the Source form of any Derivative Works
+that You distribute, all copyright, patent, trademark, and
+attribution notices from the Source form of the Work,
+excluding those notices that do not pertain to any part of
+the Derivative Works; and
+
+(d) If the Work includes a "NOTICE" text file as part of its
+distribution, then any Derivative Works that You distribute must
+include a readable copy of the attribution notices contained
+within such NOTICE file, excluding those notices that do not
+pertain to any part of the Derivative Works, in at least one
+of the following places: within a NOTICE text file distributed
+as part of the Derivative Works; within the Source form or
+documentation, if provided along with the Derivative Works; or,
+within a display generated by the Derivative Works, if and
+wherever such third-party notices normally appear. The contents
+of the NOTICE file are for informational purposes only and
+do not modify the License. You may add Your own attribution
+notices within Derivative Works that You distribute, alongside
+or as an addendum to the NOTICE text from the Work, provided
+that such additional attribution notices cannot be construed
+as modifying the License.
+
+You may add Your own copyright statement to Your modifications and
+may provide additional or different license terms and conditions
+for use, reproduction, or distribution of Your modifications, or
+for any such Derivative Works as a whole, provided Your use,
+reproduction, and distribution of the Work otherwise complies with
+the conditions stated in this License.
+
+5. Submission of Contributions. Unless You explicitly state otherwise,
+any Contribution intentionally submitted for inclusion in the Work
+by You to the Licensor shall be under the terms and conditions of
+this License, without any additional terms or conditions.
+Notwithstanding the above, nothing herein shall supersede or modify
+the terms of any separate license agreement you may have executed
+with Licensor regarding such Contributions.
+
+6. Trademarks. This License does not grant permission to use the trade
+names, trademarks, service marks, or product names of the Licensor,
+except as required for reasonable and customary use in describing the
+origin of the Work and reproducing the content of the NOTICE file.
+
+7. Disclaimer of Warranty. Unless required by applicable law or
+agreed to in writing, Licensor provides the Work (and each
+Contributor provides its Contributions) on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+implied, including, without limitation, any warranties or conditions
+of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+PARTICULAR PURPOSE. You are solely responsible for determining the
+appropriateness of using or redistributing the Work and assume any
+risks associated with Your exercise of permissions under this License.
+
+8. Limitation of Liability. In no event and under no legal theory,
+whether in tort (including negligence), contract, or otherwise,
+unless required by applicable law (such as deliberate and grossly
+negligent acts) or agreed to in writing, shall any Contributor be
+liable to You for damages, including any direct, indirect, special,
+incidental, or consequential damages of any character arising as a
+result of this License or out of the use or inability to use the
+Work (including but not limited to damages for loss of goodwill,
+work stoppage, computer failure or malfunction, or any and all
+other commercial damages or losses), even if such Contributor
+has been advised of the possibility of such damages.
+
+9. Accepting Warranty or Additional Liability. While redistributing
+the Work or Derivative Works thereof, You may choose to offer,
+and charge a fee for, acceptance of support, warranty, indemnity,
+or other liability obligations and/or rights consistent with this
+License. However, in accepting such obligations, You may act only
+on Your own behalf and on Your sole responsibility, not on behalf
+of any other Contributor, and only if You agree to indemnify,
+defend, and hold each Contributor harmless for any liability
+incurred by, or claims asserted against, such Contributor by reason
+of your accepting any such warranty or additional liability.
+
+END OF TERMS AND CONDITIONS
+
+APPENDIX: How to apply the Apache License to your work.
+
+To apply the Apache License to your work, attach the following
+boilerplate notice, with the fields enclosed by brackets "[]"
+replaced with your own identifying information. (Don't include
+the brackets!) The text should be enclosed in the appropriate
+comment syntax for the file format. We also recommend that a
+file or class name and description of purpose be included on the
+same "printed page" as the copyright notice for easier
+identification within third-party archives.
+
+Copyright [yyyy] [name of copyright owner]
+
+Licensed under the Apache License, Version 2.0 (the "License");
+you may not use this file except in compliance with the License.
+You may obtain a copy of the License at
+
+    http://www.apache.org/licenses/LICENSE-2.0
+
+Unless required by applicable law or agreed to in writing, software
+distributed under the License is distributed on an "AS IS" BASIS,
+WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+See the License for the specific language governing permissions and
+limitations under the License.

package/README.md

@@ -1,251 +1,200 @@
-# Intent DNA
+# IntentDNA
 
-**Enterprise safety control plane for AI agent behavior.**
+**Governed AI work system for turning repeated AI work methods into reviewed, distributable, locally executable workflow assets.**
 
-Intent DNA lets an organization declare safety policy once, cascade it through Species → Enterprise → Project → Personal → Role → Context → Task, and compile it into deterministic gates for every agent, project, and harness. It governs how agents operate across existing tools and systems; it does not replace your business systems or act as a domain-specific automation runtime.
+IntentDNA helps teams describe how useful AI work should happen, convert that method into a governed workflow asset, install it into local AI harnesses, collect evidence, review rollout, and improve the asset without moving runtime authority into a web dashboard.
 
----
+The product contract is:
 
-## What It Is
-
-Intent DNA is an enforcement-first control plane for organization-wide agent safety:
-
-- **Enterprise / Species policy bundles** define shared red lines across projects and teams
-- **Cascade governance** preserves provenance and prevents lower layers from relaxing organization thresholds
-- **Constraint IR** carries policy provenance into hook, SDK-check, and CI strict gates
-- **RuntimeDecisionEvent evidence** records who/what/why/from which policy for every allow/warn/block/escalate/validate decision
-- **MCP, reports, state, trace, audit, and evolution** query or package evidence; they are not the policy source of truth
+```text
+local dna is runtime truth
+marketplace distributes workflow assets
+online/SaaS manages organization evidence and lifecycle
+```
 
-It governs the agents operating on your systems rather than re-implementing the systems themselves.
+IntentDNA is not a model company, generic agent framework, prompt library, canvas automation product, or SaaS workflow executor.
 
-The core model is:
+## Install or update
 
-```text
-Enterprise / Species Policy Bundle
-  → Species→Enterprise→Project→Personal→Role→Context→Task Cascade
-  → Constraint IR + Provenance Manifest
-  → Hook / SDK-check / CI strict gate
-  → RuntimeDecisionEvent
-  → MCP / report / dashboard / evolution evidence layer
+```bash
+npm install --global intentdna@1.8.0
+dna --version
 ```
 
-For the architectural model and long-term design, see [DESIGN.md](DESIGN.md).  
-For the current stage and upcoming work, see [ROADMAP.md](ROADMAP.md).  
-For the schema contract, see [spec/schema-spec.md](spec/schema-spec.md).
+Version `1.8.0` adds the passive evidence-to-review improvement path and the Online `/create` C3 authoring guide. Online generates copyable local commands only; you still run and review them in your own project.
 
-## Design Principles
+## Product Shape
 
-- Govern agents rather than re-implementing business systems.
-- Declare enterprise safety red lines first, then compile them into native control surfaces.
-- Treat Species and Enterprise thresholds as non-relaxable by Project, Personal, Role, Context, or Task layers.
-- Keep enforcement points authoritative: hooks, SDK checks, and CI gates make decisions from compiled IR and provenance.
-- Treat runtime state, validators, traces, reports, MCP queries, and signals as evidence assets, not policy truth.
-- Keep adapters and signal ingestion pluggable so the control plane outlives any single tool.
+IntentDNA has three connected products:
 
----
+| Surface | What it owns | What it must not become |
+| --- | --- | --- |
+| Local npm foundation | `dna`, `dna-hook`, compiler, adapters, sync, reports, local runtime evidence | A thin demo wrapper or optional afterthought |
+| Workflow asset marketplace | Public, personal, `internal_ready`, and later SaaS-backed `org_private` workflow assets | Runtime execution, approval, or policy authority |
+| Online/SaaS console | Accounts, organization evidence, receipts, audit, publication lifecycle, readiness projection | A workflow runner or `allow` / `warn` / `block` / `validate` engine |
 
-## Quick Start
+The closed loop is:
 
-### Option 1: Zero-config guardrails
-
-```bash
-npm install -g intentdna
-cd your-project
-dna guard
+```text
+dogfood evidence
+  -> workflow asset
+  -> marketplace listing
+  -> local install/sync
+  -> harness execution
+  -> local runtime evidence
+  -> signed report upload
+  -> cloud receipt/audit
+  -> manager review
+  -> asset improvement
 ```
 
-### Option 2: Template-based DNA
+## Start By Role
 
-```bash
-dna init --template secure-dev
-dna sync
-```
+### Developer
 
-List templates:
+Use this when you want one governed workflow running locally without waiting for cloud setup:
 
 ```bash
-dna init --template list
+dna quickstart --asset flutter-rewrite --sync-target codex
+dna templates list
+dna templates show flutter-rewrite
+dna init --template flutter-rewrite
+dna sync --codex --dry-run
+dna sync --codex
+# run the synced workflow in Codex CLI or Claude Code
+dna report package --json
+dna report sign --json
+dna report verify <envelope-path> --json
 ```
 
-Upgrade an existing template-backed config:
+`dna quickstart` is read-only guidance: it prints the local route without initializing, syncing, running a workflow, packaging reports, signing evidence, uploading evidence, or calling Online/Supabase. Local-only use does not require Supabase. `dna sync` installs, distributes, and injects artifacts only; execution happens in the selected harness. `dna-hook` and local runtime evidence remain runtime truth.
+
+### Team Lead / Manager
+
+Use this when you need to see which workflow assets are active, blocked, stale, or ready to roll out:
 
 ```bash
-dna init --upgrade <template-name>
+dna org intake "<team/project/workflow intent>" --json
+dna org review --json
+dna org rollout --json
+dna org receipt --json
 ```
 
----
+Manager review is a read-only decision surface until an explicit local command changes project or organization state. `internal_ready` means adoption candidate, not org-private SaaS visibility. A later `org_private` publication requires auth, RLS, storage, permissions, audit, and live tests.
 
-## How It Works
+### Template Author
 
-Intent DNA compiles organization policy to your tool's native control surfaces:
+Use this when a repeated work method should become a reusable workflow asset:
 
-```text
-DNA → Cascade provenance → Constraint IR → hooks / SDK checks / CI gates → evidence
-```
-
-Typical outputs include:
-
-| Output | Purpose |
-|--------|---------|
-| `CLAUDE.md` | Behavioral guidance |
-| `.dna/compiled/ir.json` | Runtime-readable compiled constraints |
-| provenance manifest | Policy bundle, cascade layers, winners, and compiled IR hash |
-| RuntimeDecisionEvent | Enterprise evidence for allow/warn/block/escalate/validate decisions |
-| `.dna/state/sessions/*/handoffs/*.json` | Local artifact manifests for workflow handoff facts |
-| `.claude/agents/*.md` | Role definitions |
-| `.claude/skills/*/SKILL.md` | Workflow entrypoints |
-| `.claude/settings.json` or plugin runtime | Hook wiring |
-
-**Key idea:** prompts can drift, but non-relaxable enterprise thresholds, compiled gates, and provenance-backed runtime evidence make behavior governable.
-
----
-
-## Supported Workflows
-
-Intent DNA currently focuses on:
-
-- Enterprise Safety Slice: shared policy bundles, cascade provenance, and non-relaxable organization thresholds
-- Claude Code / Claude-style harnesses
-- Role-based agent workflows
-- Template-driven project bootstrap and upgrades
-- Deterministic guardrails and stateful enforcement
-- Resolver-backed artifact handoff between workflow steps
-- Evidence-layer MCP/report/state/trace/audit surfaces
-- Dogfood-driven template iteration
-
-Adapter and ecosystem direction are tracked in [ROADMAP.md](ROADMAP.md), not duplicated here.
-
----
-
-## DNA Structure (Advanced)
-
-<details>
-<summary>Click to expand</summary>
-
-```yaml
-# .dna.yaml
-version: "0.1.0"
-id: project_my_app
-name: My App
-type: project
-
-cascade:
-  inherits: ["species:default"]    # Inherit safety baseline
-  priority: 100
-
-genes:
-  code_quality:
-    description: Code quality standards
-    codons:
-      - type: attract
-        target: tested_code
-      - type: threshold
-        condition: "test_coverage >= 80%"
-        action: warn
-
-roles:
-  reviewer:
-    description: Code reviewer — read only
-    tool_permissions:
-      allow: [Read, Grep, Glob]
-      deny: [Edit, Write]
-    scope:
-      read: ["**/*"]
-    instructions:
-      - Never modify source code
-      - Give clear PASS/FAIL verdict
-
-workflows:
-  dev-pipeline:
-    name: Development Pipeline
-    steps:
-      - id: implement
-        role: implementer
-        description: Implement the feature
-      - id: review
-        role: reviewer
-        depends_on: [implement]
-        description: Review the implementation
+```bash
+dna workflow authoring-packet "<workflow intent>" --json --project-dir '<local-project-path>'
+# an external agent interviews you and writes .dna/authoring/<asset>.candidate.dna.yaml
+dna validate '<local-project-path>/.dna/authoring/<asset>.candidate.dna.yaml'
+# after explicit human confirmation, save the same YAML under .dna/templates/
+dna assets show '<asset>' --project-dir '<local-project-path>'
+dna assets inspect '<asset>' --project-dir '<local-project-path>'
+dna sync --project-dir '<local-project-path>' --dry-run
+dna sync --project-dir '<local-project-path>' --codex --dry-run
+
+# after real runs, inspect evidence-backed improvements
+dna workflow suggestions '<asset>' --json
+dna workflow review-suggestion --from-template '<asset>' --workflow '<workflow-id>' --suggestion '<suggestion-id>' --decision accept --json
+dna workflow improve-from-suggestions --from-template '<asset>' --workflow '<workflow-id>' --suggestion '<suggestion-id>' --save-template '<asset-v2>' --json
+dna workflow mine '<asset>' --json
+
+# legacy/example-assisted entry points remain available
+dna workflow intake "<workflow intent>" --json
+dna workflow route "<workflow intent>" --json
+dna workflow draft "<workflow intent>" --json # optional example-clone scaffold fallback
+dna workflow edit-plan "<change>" --from-template <template> --save-template <template-v2>
+dna assets governance <asset> --json
 ```
 
-**Cascade:** DNA files inherit and override by priority. `threshold` codons (safety rules) from Species or Enterprise are red lines: Project, Personal, Role, Context, and Task layers may add stricter rules but cannot relax them.
+Authoring starts from a work method, fit, inputs, outputs, roles, boundaries, handoffs, verifiers, and evidence posture. The external agent authors YAML; deterministic `dna validate` checks it; a human decides whether to save it. Captured evidence can produce suggestions, but only a matching human review receipt can open the next reviewable draft route. Adoption, organization binding, rollout, and sync remain separate.
 
-**Genes:** Behavioral traits (attract/repel/threshold/weight/sense).
+### Administrator / Security Buyer
 
-**Roles:** Agent identities with tool permissions and scope.
+Use this when you need to verify authority, secrets, audit, and cloud trust boundaries:
 
-**Workflows:** Multi-step procedures with retry logic.
+```bash
+dna cloud credential-check --json
+dna cloud contract-check --json
+dna cloud edge-check --json
+dna cloud deploy-plan --json
+```
 
-</details>
+Supabase is auth, persistence, storage, transport, and audit. It is not runtime governance authority. Cloud receipts must keep `runtime_authority=false`. Service role keys, secret key JSON, token pepper, Supabase access tokens, user JWTs, raw CLI API tokens, and token hashes must never be browser-facing product inputs or committed examples.
 
----
+## Quickstart
 
-## Supported Environments
+The current local quickstart is maintained in [docs/quickstart.md](docs/quickstart.md).
 
-- ✅ **Claude Code** (CLAUDE.md + hooks + agents + skills + settings)
-- 🚧 **Prompt-style adapters and markdown outputs** (.cursorrules, .clinerules, GEMINI.md)
-- 🚧 **AgentScope** (coming soon)
+Short version:
 
----
+```bash
+dna quickstart --asset flutter-rewrite --sync-target codex
+dna templates list
+dna templates show flutter-rewrite
+dna init --template flutter-rewrite
+dna sync --codex --dry-run
+dna sync --codex
+# run in Codex CLI or Claude Code
+dna report package --json
+dna report sign --json
+dna report verify <envelope-path> --json
+```
 
-## Commands
+Optional cloud upload is credential-gated and happens only after the signed local envelope verifies:
 
 ```bash
-dna guard                    # Zero-config guardrails
-dna init --template <name>   # Start from template
-dna sync <file>              # Compile DNA → harness config
-dna import .                 # Import existing config → DNA
-dna verify                   # Check config integrity
-dna feedback --evolve        # Preview marker changes from local classified signals
-dna evolve <dna-id>          # Preview marker changes from persisted outcomes
-dna sync <file> --evolve     # Mutating path: apply evolved markers before sync
+dna cloud credential-check --json
+dna cloud deploy-plan --json
+dna report upload <envelope-path> --json
 ```
 
----
+## Core Boundaries
 
-## Philosophy
+- Local `dna` and `dna-hook` remain runtime truth.
+- Online never executes workflows and never performs `allow`, `warn`, `block`, or `validate`.
+- `dna sync` installs, distributes, and injects artifacts; it does not execute workflows.
+- Marketplace distributes workflow assets and install plans; it does not approve, install, or execute them.
+- Supabase persists identity, reports, receipts, storage refs, and audit events; it does not enforce runtime policy.
+- Browser-local imports and Online demo states are projection only until trusted upload verifies them.
+- MCP is hidden transport, not a product page or auth surface.
+- `org_private` must not appear in the static marketplace catalog before SaaS auth/RLS/storage/permission/audit gates exist.
 
-**Intent DNA** is inspired by biological DNA:
+## Evidence Model
 
-- **Genes** encode behavioral traits
-- **Codons** are the atomic instructions
-- **Cascade** mimics inheritance and override rules
-- **Epigenetics** learns from experience without mutating source intent
+IntentDNA separates evidence from authority:
 
-Read more: [DESIGN.md](DESIGN.md)
+| Evidence | Meaning |
+| --- | --- |
+| Local report package | Runtime evidence gathered locally from harness and verifier outputs |
+| Signed envelope | Local package hash/signature can be checked before upload |
+| Local org review receipt | Manager review and publication readiness handoff; not cloud membership proof |
+| Cloud ingest receipt | Trusted upload evidence after Supabase function/storage/audit accepts it |
+| Online projection | Human-readable status and lifecycle view; not runtime truth |
 
----
+Trusted cloud ingestion may increase persistence and visibility, but it does not move runtime authority away from local `dna-hook` and local runtime evidence.
 
 ## Documentation Map
 
-- [DESIGN.md](DESIGN.md) — long-term architecture and design
-- [ROADMAP.md](ROADMAP.md) — current stage, next plan, deferred work
-- [docs/README.md](docs/README.md) — Repo-Wiki root and reading paths
-- [spec/README.md](spec/README.md) — engineering spec index and status map
-- [spec/schema-spec.md](spec/schema-spec.md) — schema contract
-- [docs/references/](docs/references/) — distilled research and implementation references
-- [docs/workflows/](docs/workflows/) — operational runbooks
-- [docs/troubleshooting/](docs/troubleshooting/) — troubleshooting entry points
-- [docs/insights/](docs/insights/) — strategic and product-thinking documents
+- [docs/README.md](docs/README.md) - living docs map and two-state documentation rule.
+- [docs/quickstart.md](docs/quickstart.md) - local developer quickstart.
+- [docs/product/milestone-review-protocol.md](docs/product/milestone-review-protocol.md) - lightweight P-stage review protocol.
+- [docs/product/online-product-spec.md](docs/product/online-product-spec.md) - Online IA, K5 boundary, forbidden copy, and acceptance.
+- [docs/decisions/ADR-001-product-reset.md](docs/decisions/ADR-001-product-reset.md) - product reset decision record.
+- [spec/README.md](spec/README.md) - retained technical spec index.
+- [docs/archive/2026H1/INDEX.md](docs/archive/2026H1/INDEX.md) - archived references, insights, historical specs, runbooks, and one-time materials.
+
+## Current Maturity
 
----
+- Local foundation: active.
+- Template marketplace: active for public/personal assets; `internal_ready` is a review candidate state.
+- Org-private marketplace: SaaS-gated; requires Supabase auth/RLS/storage/permissions/audit and live tests.
+- Online console: projection/workbench/readiness surface; not workflow runtime.
+- Public release, npm publish, and production SaaS claims require fresh build/test/deploy evidence before being claimed.
 
 ## License
 
 Apache-2.0
-
----
-
-## Contributing
-
-Issues and PRs welcome. See [ROADMAP.md](ROADMAP.md) for planned features.
-
----
-
-## Related Projects
-
-- [Superpowers](https://github.com/superpowersai/superpowers) — 123K users, skill-based agent workflows
-- [Cline KanBan](https://github.com/cline/cline-kanban) — Multi-agent task orchestration
-- [AgentScope](https://github.com/modelscope/agentscope) — Multi-agent framework from Alibaba
-
-Intent DNA is designed to compile into the native control surfaces those frameworks expose, with current maturity varying by adapter.