Impact & VisionBounded

Impact metrics

The planned measurement surface and the current release boundary. AIJIM does not yet claim server-attested impact metrics as product truth.

Current release boundary

Impact metrics are not presented as live, hash-verified, or forensic product evidence in the current release. The valid posture is planned measurement plus honest absence until server-attested aggregation exists.

Current truth

Runtime status

Impact instrumentation exists, but server-attested aggregation is not the active release authority.

Tooling status

LINA impact placeholder tools return unavailable instead of successful synthetic data.

Claim boundary

Docs may discuss planned impact measurement, but must not claim hash-verified impact metrics yet.

Next closure

Implement Core-owned aggregation, durable evidence capture, and release evidence before enabling impact KPIs as product truth.

Candidate signal set

These are the signals AIJIM should aggregate once the server-owned measurement layer is available. They are design targets, not active release claims.

Stories Published

Publication output once Core-owned publication evidence is present

Claims Reviewed

Human review decisions grouped by workspace and story

Draft Runs

Core-backed draft-run records, not client-fabricated counts

Evidence Bindings

Claim-to-evidence support coverage from durable story state

Review Gates

Reviewer/editorial/expert gate outcomes from Core authority

Release Readiness

Derived from available verifier/export evidence, not a standalone KPI claim

Implementation requirement

A future impact dashboard must be Core-backed, workspace-scoped, tenant-safe, and release-evidenced. Client-only counters, placeholder tool responses, or unreviewed telemetry cannot elevate into impact proof.