Forge Platform

Handbook

Platform assay log — M0

Assay rubric: prompts/shared/platform-review-assay.md.

Docs and contracts reviewed (Composer 02 scope):

Result

Status: warning

Assessment date: 2026-05-17

Reviewer: Maintainer review (automated prep + human OK on merge)

Rubric checklist (8)

  1. Lenses control plane — Pass. Charter loop ends in Lenses review; product boundaries and ADR-0001 keep Lenses as human-facing control and system of record.
  2. Blueprints = policy, not runtime — Pass. Boundaries table and security model separate canonical policy from live run state.
  3. LCDL = governed reasoning, not orchestration — Pass. Charter places LCDL before approval; ADR-0004 and boundaries forbid execution/UI ownership.
  4. Fleet = execution, not planning — Pass. ADR-0003 and boundaries keep templates/execution; planning stays outside Fleet.
  5. Agents as workcells — Pass. Charter + ADR-0002 + WorkcellRequest / WorkcellResult narrative align.
  6. Human approval explicit — Pass. Security model human gates; approval_mode on ForgeRun / WorkcellRequest with enum alignment.
  7. Evidence for human decision — Pass. EvidencePacket purpose and required fields support review; redaction expectations documented.
  8. Boundaries blurred — No critical blur in reviewed docs; see risks below for documentation/schema gaps (not ownership inversions).

Boundary risks observed

  • Named contract without v1 JSON schema: ForgeRunStatusSummary appears in docs/intersection-map.md (OpenClaw row) and OpenClaw prompts, but there is no matching schemas/*.schema.json yet. Runtime teams may invent divergent shapes unless M6 defines it or the map points to an existing type (e.g. slim ForgeRun projection).
  • Cross-product approval_mode enforcement is specified in schemas and security model; actual product UIs must not introduce silent modes—track as integration Spark, not a charter rewrite.

Missing contracts / follow-ups

Item Severity Suggested Spark or ADR
ForgeRunStatusSummary (or explicit alias to ForgeRun fields) for OpenClaw ↔ Lenses Medium SPK-M6-status-contract — add schema or remove/rename map row until done
Optional: EvidenceSummary vs full EvidencePacket for channel relay Low Document in M6 charge or OpenClaw prompt only

Notes

  • Composer 05 (schema pass): See compatibility note at bottom of foundation-check.log.md.

  • No broad rewrites performed per Composer 02 instruction; charter, boundaries, intersection map, and security model are internally consistent with ADRs and sample JSON for forge.run.v1 / forge.evidence_packet.v1.