Product signal atlasProduct signal atlasCurrent / Adoption

Product signal atlas

Fictional sample. Every metric, status, organization, and decision on this page exists only to demonstrate the report engine; replace it with verified project evidence before use.

Every visual below is authored as bounded Markdown directives. The compiler validates the data and emits deterministic SVG or semantic HTML; the page performs no visualization-time network request.

Adoption signal

Weekly active agentsActive agents increased across four weekly releases, with the assisted cohort leading after week two.
Weekly active agentsActive agents increased across four weekly releases, with the assisted cohort leading after week two. Data: Assisted, W1: 42; Assisted, W2: 68; Assisted, W3: 91; Assisted, W4: 128; Baseline, W1: 38; Baseline, W2: 51; Baseline, W3: 63; Baseline, W4: 74.050100150W1W2W3W4Release weekActive agents050100150W1W2W3W4Release weekActive agents
  • Assisted
  • Baseline

Quality trend

Successful first buildsThe percentage of agents completing a successful first build rose during the measured releases.
Successful first buildsThe percentage of agents completing a successful first build rose during the measured releases. Data: Success rate, W1: 61.5; Success rate, W2: 70; Success rate, W3: 82.5; Success rate, W4: 91.0255075100W1W2W3W4Release weekPercent0255075100W1W2W3W4Release weekPercent
  • Success rate

Work mix

Generated page mixReports are the largest category, followed by tutorials, dashboards, and landing pages.
Generated page mixReports are the largest category, followed by tutorials, dashboards, and landing pages. Data: Pages, Reports: 46; Pages, Tutorials: 24; Pages, Dashboards: 18; Pages, Landing pages: 12.46%24%18%12%46%24%18%12%
  • Reports
  • Tutorials
  • Dashboards
  • Landing pages

Compilation flow

Offline compilation flowFifteen participants across authoring, compilation, and artifact subsystems.
Offline compilation flowFifteen participants across authoring, compilation, and artifact subsystems. Nodes: 15; flow layers: 8. Groups: “Authoring graph”: Declarative source, Markdown partials, Local assets, Manifest metadata, Review sidecar; “Compiler pipeline”: Validate data, Confine resources, Highlight code, Compile visuals, Serialize output; “Portable artifact”: Semantic HTML, Package styles, Reader runtime, Review targets, Portable artifact. Layers along the flow: 1. Declarative source [Input and output]; Markdown partials; Local assets; Manifest metadata; Review sidecar. 2. Validate data. 3. Confine resources. 4. Highlight code. 5. Compile visuals [Rendering step]. 6. Serialize output. 7. Semantic HTML; Package styles; Reader runtime; Review targets. 8. Portable artifact [Input and output]. Connections along the flow: Declarative source → Validate data: parse; Markdown partials → Validate data: expand; Local assets → Confine resources: resolve; Manifest metadata → Validate data: normalize; Review sidecar → Review targets: bind; Validate data → Confine resources: typed graph; Confine resources → Highlight code: safe source; Highlight code → Compile visuals: styled HAST; Compile visuals → Serialize output: semantic tree; Serialize output → Semantic HTML: document; Serialize output → Package styles: theme; Serialize output → Reader runtime: behavior; Serialize output → Review targets: provenance; Semantic HTML → Portable artifact: assemble; Package styles → Portable artifact: package; Reader runtime → Portable artifact: interact; Review targets → Portable artifact: review.Authoring graphCompiler pipelinePortable artifactDeclarative sourceMarkdown partialsLocal assetsManifest metadataReview sidecarValidate dataConfine resourcesHighlight codeCompile visualsSerialize outputSemantic HTMLPackage stylesReader runtimeReview targetsPortable artifactparseexpandresolvenormalizebindtyped graphsafe sourcestyled HASTsemantic treedocumentthemebehaviorprovenanceassemblepackageinteractreview
  • Input and output
  • Rendering step
Diagram in words

Nodes: 15; flow layers: 8.

Groups

  • “Authoring graph”: Declarative source, Markdown partials, Local assets, Manifest metadata, Review sidecar
  • “Compiler pipeline”: Validate data, Confine resources, Highlight code, Compile visuals, Serialize output
  • “Portable artifact”: Semantic HTML, Package styles, Reader runtime, Review targets, Portable artifact

Layers along the flow

  1. Declarative source [Input and output]; Markdown partials; Local assets; Manifest metadata; Review sidecar
  2. Validate data
  3. Confine resources
  4. Highlight code
  5. Compile visuals [Rendering step]
  6. Serialize output
  7. Semantic HTML; Package styles; Reader runtime; Review targets
  8. Portable artifact [Input and output]

Connections along the flow

  • Declarative source → Validate data: parse
  • Markdown partials → Validate data: expand
  • Local assets → Confine resources: resolve
  • Manifest metadata → Validate data: normalize
  • Review sidecar → Review targets: bind
  • Validate data → Confine resources: typed graph
  • Confine resources → Highlight code: safe source
  • Highlight code → Compile visuals: styled HAST
  • Compile visuals → Serialize output: semantic tree
  • Serialize output → Semantic HTML: document
  • Serialize output → Package styles: theme
  • Serialize output → Reader runtime: behavior
  • Serialize output → Review targets: provenance
  • Semantic HTML → Portable artifact: assemble
  • Package styles → Portable artifact: package
  • Reader runtime → Portable artifact: interact
  • Review targets → Portable artifact: review

Compile request sequence

Compile request sequenceOne offline build crosses four participants in authored message order.
Compile request sequenceOne offline build crosses four participants in authored message order. Participants: 4; messages: 4. Participants from left to right: Authoring agent; Source loader; Compiler; Browser. Messages in order: 1. Authoring agent → Source loader: load source. 2. Source loader → Compiler: validated graph. 3. Compiler → Browser: write artifact. 4. Browser → Authoring agent: review result.AuthoringagentSource loaderCompilerBrowserload sourcevalidated graphwrite artifactreview result
Diagram in words

Participants: 4; messages: 4.

Participants from left to right

  • Authoring agent
  • Source loader
  • Compiler
  • Browser

Messages in order

  1. Authoring agent → Source loader: load source
  2. Source loader → Compiler: validated graph
  3. Compiler → Browser: write artifact
  4. Browser → Authoring agent: review result

Delivery path

Release journeyFour milestones move the product from evidence to a locally verified release candidate.

  1. Inspect the catalog

    The agent reads the registry-derived source contract and chooses supported primitives.

  2. Write compact data

    Charts, nodes, edges, and events remain ordinary directive attributes and Markdown.

  3. Compile offline

    The same validated model produces single-file or directory output.

  4. Open through file://

    Desktop and mobile checks inspect the real generated artifact without a server.

  • Authoring
  • Automatic build
  • Needs checking

Contents