Skip to content

docs(roadmap): sync canonical planning - #319

Open
nicolasmelo1 wants to merge 1 commit into
mainfrom
automation/planning-mirror-34304562775
Open

docs(roadmap): sync canonical planning#319
nicolasmelo1 wants to merge 1 commit into
mainfrom
automation/planning-mirror-34304562775

Conversation

@nicolasmelo1

Copy link
Copy Markdown
Owner

Generated from canonical planning commit 31b8ea8b1aab8817b2534fd177a9e8c6abd1c888. Review the public projection and manifest; this workflow never pushes directly to main.

Signed-off-by: logion-roadmap-bot <logion-roadmap-bot@users.noreply.github.com>

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Changes recommended

Several newly added Markdown links use unescaped spaces/colons in the link destination (e.g., “../maintainer documentation: …”), which renders as broken links on GitHub and is likely to fail documentation link integrity checks.

Once you've addressed the issues Copilot identified, you can request another Copilot review.

Pull request overview

Syncs the public planning projection (plans/, future-roadmap/) from the canonical planning source, updating the 0.2 release roadmap and related Phase 16 planning documents, and refreshing the sync manifest used to track the projection.

Changes:

  • Expands the 0.2 release plan with clearer evaluation-scope boundaries and updated public-surface requirements.
  • Adds new planning documents for the “public answer surface” and Phase 16.1.x planning cadence, plus a “driven actor” corrective plan.
  • Updates multiple Phase 16 docs to tighten environment identity language (harness stack + iteration budget) and aligns roadmap references after retiring older phase plan files.
File summaries
File Description
plans/release-0.2.md Updates 0.2 scope, gate checklist, and clarifies evaluation vs sustained-use boundaries.
plans/public-answer-surface.md Adds a new plan defining a zero-install public “does it work?” answer surface and its constraints.
plans/positioning-and-independence.md Adjusts positioning/wedge narrative and adds stricter public-copy language discipline.
plans/phase-16.9-benchmark-field-reconciliation.md Tightens reconciliation compatibility to include harness stack + iteration budget.
plans/phase-16.5-eval-attestations-and-cross-node-authority.md Expands attestation requirements to include harness stack + iteration budget.
plans/phase-16.4-deterministic-replication-and-agreement.md Clarifies replication equivalence boundaries around harness stack + iteration budget.
plans/phase-16.2-typed-evaluators-and-skill-reference-evaluator.md Tightens control/assisted comparability requirements and updates the builtin scenario name.
plans/phase-16.1.5-what-is-installed-here-has-a-version.md Adds a new plan focusing on local installed artifact version identity + attribution gaps.
plans/phase-16.1.4-a-published-entry-resolves.md Adds a new plan documenting AI Catalog/OpenAPI/idempotency issues and acceptance criteria.
plans/phase-16.1.3-the-documentation-is-read-out-of-the-code.md Adds a new plan to derive docs/indexes from code via marker blocks and checks.
plans/phase-16.1.2-a-plan-is-one-pull-request.md Adds a new plan establishing a ceiling on phase assertion count and enabling proof-budget checks.
plans/phase-16.1.1-a-gate-outlives-its-plan.md Adds a new plan defining archive/docs integrity rules and retirement mechanics.
plans/phase-16.1-eval-contract-and-reference-runner.md Expands environment identity requirements (harness stack/model/budget) and implementation guidance.
plans/phase-15.15-isolated-first-runner-node.md Updates builtin scenario naming and records sealed status notes.
plans/phase-15.14.1-local-multi-agent-first-node-foundation.md Updates builtin scenario naming and records sealed status notes.
plans/phase-15.12-ai-catalog-publication-and-ard-discovery.md Removes this retired plan document from plans/.
plans/phase-15.11-native-use-observation-linked-feedback-and-reviews.md Removes this retired plan document from plans/.
plans/phase-15.10.1-deepseek-harness-adapter-and-logion-dsh-plugin.md Removes this retired plan document from plans/.
plans/phase-15.10-native-acquisition-artifact-delivery-and-inventory.md Removes this retired plan document from plans/.
plans/normative-carry-overs.md Updates carry-over contracts, including envelope resolution notes and “designed, not built” publisher path.
plans/next-steps.md Updates the execution order, statuses, and references (including new step 5a/5c/5d structure).
plans/driven-actor-performs-the-measured-flow.md Adds a new plan to correct “mute driven actor” evidence flow issues in scenarios.
plans/consumption-adoption-ladder.md Updates references to shipped shapes and revised publisher-integrated path pointers.
future-roadmap/open-protocol-and-entitlement-portability.md Updates roadmap references to the newer doc locations for AI Catalog/ARD discovery.
future-roadmap/human-dashboard-and-user-policy.md Updates roadmap references to the newer doc locations for native inventory/consent.
docs/roadmap-sync-manifest.json Refreshes the sync manifest entries and source revision for this projection.
Review details

Suppressed comments (6)

plans/release-0.2.md:349

  • This link destination includes a space/colon, which breaks Markdown parsing on GitHub (it will link to "../maintainer"). Use a code-styled reference (or a real repo-relative path) instead.
3. [the publication playbook](../maintainer documentation: measurement-publication-playbook.md)

plans/release-0.2.md:479

  • This Markdown link destination contains an unescaped space, so the rendered link will be wrong/broken. Use a code-styled reference (or an actual path) instead.
      [playbook](../maintainer documentation: measurement-publication-playbook.md) says

future-roadmap/open-protocol-and-entitlement-portability.md:65

  • This link destination contains an unescaped space/colon, which breaks the rendered link on GitHub. Use a code-styled reference (or a real repo-relative path) instead.
| PDS (self-hosted user data server, permissionless) | Resource/evidence node | AI Catalog publication + ARD discovery in [`maintainer documentation: ai-catalog-and-ard-discovery.md`](../maintainer documentation: ai-catalog-and-ard-discovery.md), AKTP events in [`plans/phase-15.17`](../plans/phase-15.17-aktp-evidence-and-improvement-feed-v0.md) |

future-roadmap/open-protocol-and-entitlement-portability.md:273

  • This link destination contains an unescaped space/colon and will render as a broken link on GitHub. Prefer a code-styled reference (or a real path) instead.
| v0 — indexed resources | AI Catalog publisher/consumer + ARD Agent Finder indexer + optional AKTP evidence/improvement link | **None needed.** Discovery is open; settlement remains node-local | [`maintainer documentation: ai-catalog-and-ard-discovery.md`](../maintainer documentation: ai-catalog-and-ard-discovery.md), [`plans/phase-15.17`](../plans/phase-15.17-aktp-evidence-and-improvement-feed-v0.md) |

plans/consumption-adoption-ladder.md:53

  • This link destination contains an unescaped space/colon, so the rendered link will be wrong/broken. Prefer a code-styled reference (or a real repo-relative path) here.
[Native-use observation](../maintainer documentation: native-use-observation-and-feedback.md) owns this surface.

future-roadmap/open-protocol-and-entitlement-portability.md:146

  • This link destination contains an unescaped space/colon, so GitHub will parse it incorrectly. Use a code-styled reference (or a real path) to avoid broken links.
1. **v0 — self-announce.** `POST /v1/nodes/announce {host}` on the index
   + `logion node announce` in the CLI (the requestCrawl pattern; spec and
   abuse bounds were superseded by ARD ingestion in [`maintainer documentation: ai-catalog-and-ard-discovery.md`](../maintainer documentation: ai-catalog-and-ard-discovery.md)
   §2.6). An announce buys one validated well-known fetch, never a
   listing. Seed yaml remains as bootstrap, never as gate.
  • Files reviewed: 27/27 changed files
  • Comments generated: 5
  • Review effort level: Lite

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

Comment on lines 17 to 20
Native inventory plus `off|local-only|prompt|auto` feedback consent lands earlier
in [`plans/phase-15.10`](../plans/phase-15.10-native-acquisition-artifact-delivery-and-inventory.md)
and [`plans/phase-15.11`](../plans/phase-15.11-native-use-observation-linked-feedback-and-reviews.md);
in [`maintainer documentation: native-acquisition-and-inventory.md`](../maintainer documentation: native-acquisition-and-inventory.md)
and [`maintainer documentation: native-use-observation-and-feedback.md`](../maintainer documentation: native-use-observation-and-feedback.md);
the dashboard must configure those existing policies rather than inventing a second
Comment on lines +39 to 40
([`maintainer documentation: ai-catalog-and-ard-discovery.md`](../maintainer documentation: ai-catalog-and-ard-discovery.md));
an optional catalog entry relation/discovery extension advertises the AKTP evidence/improvement feed
```

Logion may recommend or delegate to these commands, but it does not silently replace them. Phase [`15.10`](phase-15.10-native-acquisition-artifact-delivery-and-inventory.md) adds:
Logion may recommend or delegate to these commands, but it does not silently replace them. Shipped, per [`native-acquisition-and-inventory.md`](../maintainer documentation: native-acquisition-and-inventory.md):
Comment on lines +212 to +213
about a named third party without the author contact step in
[`../maintainer documentation: measurement-publication-playbook.md`](../maintainer documentation: measurement-publication-playbook.md).
Comment thread plans/release-0.2.md
Comment on lines +175 to +178
an earlier step is invisible to the unit Logion records. Say that, in the layer
label and in the disclaimer. Under
[`../maintainer documentation: measurement-publication-playbook.md`](../maintainer documentation: measurement-publication-playbook.md)
a stated blind spot is also a demand signal for what to measure next.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants