design_doc · json

Agent JSON, Human HTML: Forge Standard

Governed RedKey work should be canonical JSON for agents and systems, rendered as intentional Dreamborn Forge HTML for humans.

Planning Surface

Use this to decide what happens next.

Status

draft

Agent Handoff

Start Here

Governed RedKey work should be canonical JSON for agents and systems, rendered as intentional Dreamborn Forge HTML for humans.

Completion Evidence

No explicit evidence field yet. Require tests, screenshots, linked PRs, or reviewed outputs before marking complete.

Thesis

Governed RedKey work should be canonical JSON for agents and systems, rendered as intentional Dreamborn Forge HTML for humans.

Implementation Plan

Forge artifact pair: Create JSON and Forge HTML examples for this standard.
Forge audit: Add a first-pass script that checks generated HTML for Forge compliance.
Renderer contracts: Define reusable Forge renderer contracts for design_doc, decision_record, and build_execution.
Knowledge Console: Use Forge renderers to traverse artifacts, design specs, design systems, agents, decisions, and builds.

Sections

Why this matters: JSON gives agents deterministic contracts. Forge HTML gives Justin a readable operating surface. Enforcing both prevents Markdown sprawl and visual drift.
Operating contract: id: string, title: string, items: object
Enforcement: id: string, title: string, items: object