82a358f18d
ontoref-derive: #[onto_mcp_tool] attribute macro registers MCP tool unit-structs in
the catalog at link time via inventory::submit!; annotated item is emitted unchanged,
ToolBase/AsyncTool impls stay on the struct. All 34 tools migrated from manual wiring
(net +5: ontoref_list_projects, ontoref_search, ontoref_describe,
ontoref_list_ontology_extensions, ontoref_get_ontology_extension).
validate modes (ADR-018): reads level_hierarchy from workflow.ncl and checks every
.ncl mode for level declared, strategy declared, delegate chain coherent, compose
extends valid. mode resolve <id> shows which hierarchy level handles a mode and why.
--self-test generates synthetic fixtures in a temp dir for CI smoke-testing.
validate run-cargo: two-step Cargo.toml resolution — workspace layout first
(crates/<check.crate>/Cargo.toml), single-crate fallback by package name or repo
basename. Lets the same ADR constraint shape apply to workspace and single-crate repos.
ontology/schemas/manifest.ncl: registry_topology_type contract — multi-registry
coordination, push targets, participant scopes, per-namespace capability.
reflection/requirements/base.ncl: oras ≥1.2.0, cosign ≥2.0.0, sops ≥3.9.0, age
≥1.1.0, restic declared as Hard/Soft requirements with version_min, check_cmd, and
install_hint (ADR-017 toolchain surface).
ADR-019: per-file recipient routing for tenant isolation without multi-vault. Schema
additions: sops.recipient_groups + sops.recipient_rules in ontoref-project.ncl.
secrets-bootstrap generates .sops.yaml from project.ncl in declarative mode. Three
new secrets-audit checks: recipient-routing-coherent, recipient-routing-coverage,
no-multi-vault. Adoption templates: single-team/, multi-tenant/, agent-first/.
Integration templates: domain-producer/, mode-producer/, mode-consumer/.
UI: project_picker surfaces registry badge (⟳ participant) and vault badge
(⛁ vault_id · N, green=declarative / amber=legacy) per project card. Expanded panel
adds collapsible Registry section with namespace, endpoint, and push/pull capability.
manage.html gains Runtime Services card — MCP and GraphQL toggleable without restart
via HTMX POST /ui/manage/services/{service}/toggle.
describe.nu: capabilities JSON includes registry_topology and vault_state per project.
sync.nu: drift check extended to detect //! absence on newly registered crates.
qa.ncl: six entries — credential-vault-best-practice (layered data-flow diagram),
credential-vault-templates (paths A/B/C), credential-vault-troubleshooting (15 named
errors), integration-what-and-why (ADR-042 OCI federation), integration-how-to-implement,
integration-troubleshooting.
on+re: core.ncl + manifest.ncl updated to reflect OCI, MCP, and mode-hierarchy nodes.
Deleted stale presentation assets (2026-02 slides + voice notes).
62 lines
2 KiB
XML
62 lines
2 KiB
XML
{
|
|
id = "0015",
|
|
slug = "registry-topology",
|
|
description = "Declare registry_provides in .ontology/manifest.ncl with participant id and namespace topology. Domain artifacts now use domains/<participant>/<id>:<version> instead of the flat domains/<id>:<version> namespace.",
|
|
|
|
check = {
|
|
tag = "Grep",
|
|
paths = [".ontology/manifest.ncl"],
|
|
pattern = "registry_provides",
|
|
},
|
|
|
|
instructions = "
|
|
## Registry topology declaration (migration 0015)
|
|
|
|
The provisioning registry now uses participant-scoped namespaces for all artifacts:
|
|
domains/<participant>/<id>:<version>
|
|
modes/<participant>/<id>:<version> (already correct if you used mode-push)
|
|
|
|
### Step 1 — Declare registry_provides in .ontology/manifest.ncl
|
|
|
|
Add inside your make_manifest { ... }:
|
|
|
|
registry_provides = m.make_registry_provides {
|
|
participant = \"<your-project-id>\",
|
|
registries = m.make_registries_config {
|
|
default = \"primary\",
|
|
registries = [
|
|
m.make_registry_entry {
|
|
id = \"primary\",
|
|
endpoint = \"\",
|
|
role = 'primary,
|
|
tls = true,
|
|
namespaces = {
|
|
own = [\"domains/<your-project-id>/\", \"modes/<your-project-id>/\"],
|
|
prefixes = [\"domains/<your-project-id>/\", \"modes/<your-project-id>/\"],
|
|
},
|
|
},
|
|
],
|
|
},
|
|
},
|
|
|
|
Set endpoint = \"\" and configure PROVISIONING_REGISTRY at runtime, or fill it in
|
|
once the registry hostname is stable.
|
|
|
|
### Step 2 — Update domain-push calls (participant is now positional arg 2)
|
|
|
|
# Before
|
|
domain-push <path> --registry <reg>
|
|
# After
|
|
domain-push <path> <your-project-id> --registry <reg>
|
|
|
|
### Step 3 — Update domain-pull / describe / verify (use participant/id form)
|
|
|
|
# Before: domain-pull <id> <version>
|
|
# After: domain-pull <participant> <id> <version>
|
|
# or via: prvng i domain pull <participant>/<id> <version>
|
|
|
|
### Step 4 — Verify live state
|
|
|
|
PROVISIONING_REGISTRY=<host> ore provisioning i list --live
|
|
",
|
|
}
|