Skip to content

docs(main-path): name the new product surface verbs #751

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Birfy merged 1 commit into from
Nov 5, 2026
Merged

docs(main-path): name the new product surface verbs #751

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions changelog.d/751-main-path-surfaces.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
Changed
`docs/main-path.md` now names the product verbs added around the three supported
paths: independent release-receipt verification, `platform status` over the
durable run store, `ops history`, governed-harness approval decisions, and the
persistent tenant registry report. Docs only; no runtime behavior changes.
16 changes: 11 additions & 5 deletions docs/main-path.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,8 +45,10 @@ paired scores -> TrustEvidence -> PromotionDecision -> signed ReleaseRecord
| admission (optional) | `policy_release` (signed manifest + admission, not a second decision engine) |

`agentdescent release` and the MCP `release` tool are the product surface.
Do not hand-wire the three steps in application code; use `release_pipeline` or
the CLI.
`agentdescent release verify` (and MCP `release_verify`) checks the signed
receipt independently: it recomputes the signature over the embedded manifest
and can pin the expected key id and lineage node. Do not hand-wire the three
steps in application code; use `release_pipeline` or the CLI.

## Path C — continuous platform

Expand All @@ -68,15 +70,19 @@ LoopKernel (durable) -> RSIPlatform (five layers) -> PlatformCampaign (multi-cyc
when you need a single session with acceptance/decision logging; use
`RSIPlatform` when the five layers must hand off to each other.

`agentdescent platform status` (and MCP `platform_status`) reads a finished
campaign's run database without the compute, foundry or experience callbacks;
it only inspects the durable run store.

## Advanced layers (supported, narrower)

| layer | canonical modules | surface |
|---|---|---|
| capability growth | `task_pipeline`, `capability_scout`, `capability_foundry`, `capability_archive`, `capability_loop` | `agentdescent capability` |
| tenancy | `workspaces`, `tenant_platform` | `agentdescent tenant` |
| operations | `ops_fabric` (write), `ops_console` (read), `rsi_metrics`, `rsi_telemetry`, `campaign_ops` | `agentdescent ops` |
| tenancy | `workspaces`, `tenant_platform` | `agentdescent tenant` (`plan`, `run`) |
| operations | `ops_fabric` (write), `ops_console` (read), `rsi_metrics`, `rsi_telemetry`, `campaign_ops` | `agentdescent ops` (`plan`, `publish`, `history`) |
| meta-learning | `meta` (including `continuous_meta_run`), `meta_curriculum`, `meta_population`, `meta_campaign`, `meta_audit`, `meta_exam`, `verified_seed` | `agentdescent meta-campaign`, `exam`, `audit` |
| governed harness | `safe_selfmod`, `proofs`, `approval`, `safety_controller`, `governed_harness` | `agentdescent governed-harness` |
| governed harness | `safe_selfmod`, `proofs`, `approval`, `safety_controller`, `governed_harness` | `agentdescent governed-harness` (`plan`, `run`, `approvals`, `approve`, `reject`) |

These are not “extra algorithms”; they are the control, evidence and memory
layers around the three paths.
Expand Down
Loading