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.0326496128W1W2W3W4Release 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.022.7545.568.2591W1W2W3W4Release 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%
  • 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. Groups: authoring: Authoring graph (source, partials, assets, manifest, review); compiler: Compiler pipeline (validate, confine, highlight, render, serialize); artifact: Portable artifact (html, styles, runtime, targets, portable). Nodes: source: Declarative source; partials: Markdown partials; assets: Local assets; manifest: Manifest metadata; review: Review sidecar; validate: Validate data; confine: Confine resources; highlight: Highlight code; render: Compile visuals; serialize: Serialize output; html: Semantic HTML; styles: Package styles; runtime: Reader runtime; targets: Review targets; portable: Portable artifact. Connections: source to validate: parse; partials to validate: expand; assets to confine: resolve; manifest to validate: normalize; review to targets: bind; validate to confine: typed graph; confine to highlight: safe source; highlight to render: styled HAST; render to serialize: semantic tree; serialize to html: document; serialize to styles: theme; serialize to runtime: behavior; serialize to targets: provenance; html to portable: assemble; styles to portable: package; runtime to portable: interact; targets to portable: review.Authoring graphCompiler pipelinePortable artifactparseexpandresolvenormalizebindtyped graphsafe sourcestyled HASTsemantic treedocumentthemebehaviorprovenanceassemblepackageinteractreviewDeclarative sourceMarkdown partialsLocal assetsManifest metadataReview sidecarValidate dataConfine resourcesHighlight codeCompile visualsSerialize outputSemantic HTMLPackage stylesReader runtimeReview targetsPortable artifact

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: agent: Authoring agent; loader: Source loader; compiler: Compiler; browser: Browser. Messages in order: 1. agent to loader: load source; 2. loader to compiler: validated graph; 3. compiler to browser: write artifact; 4. browser to agent: review result.Authoring agentSource loaderCompilerBrowserload sourcevalidated graphwrite artifactreview 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.

Contents

Review workspace

Review this report

No discussion threads yet