Findings and planning reports in one workbench
Review Guard results, findings, generated objectives, key results, Epics and supporting planning details without digging through separate artifacts or pull-request logs.
DECIDE · IAAP CONSOLE
IaaP Console is a customer-hosted review experience for verified Guard evidence, Forge product visibility, traceability and human workbenches. It consumes versioned producer contracts rather than quietly reimplementing their logic.
THE PROBLEM
A platform team may have findings in pull requests, product proposals in another repository, evidence digests in artifacts and human review happening somewhere else. Console creates a coherent review surface while preserving the source of truth: producers keep ownership of their verdicts and proposals, and reviewers can verify what they are looking at before acting on it.
WHAT YOU ACTUALLY GET
Console turns Guard and Forge outputs into a customer-controlled review workspace. It helps people find, verify and understand the material without changing the underlying verdicts or product proposals.
Review Guard results, findings, generated objectives, key results, Epics and supporting planning details without digging through separate artifacts or pull-request logs.
See Forge product definitions, proposal context, lifecycle state and supporting evidence so reviewers understand what product is being discussed and where it stands.
Search, filter and inspect findings, planning output and product context so architecture, security, product and audit users can focus on the material relevant to them.
Console retains producer revision, digest and evidence lineage so a reviewer can trace what is displayed back to the Guard or Forge material that produced it.
Human reviewers get a workspace for review context, materiality, notes and bounded workflow markers without Console silently turning those aids into approval authority.
Generate bounded manifests and review-ready exports that retain source history for audits, architecture reviews, governance discussions and handoffs.
Console is the place to understand and review the work. It does not rewrite Guard findings, change Forge proposals, approve infrastructure or become a second control plane.
SIGNATURE REVIEW MODEL
Console binds what a reviewer sees back to pinned producer evidence, presents it through a customer-controlled workbench, and keeps the actual decision outside Console's authority.
Pinned source
Versioned contract
Evidence digest
Digest match
Fail closed
Retain provenance
Inspect · filter · trace
Review markers · notes
Bounded visibility
Customer controlled
Materiality context
Authorized decision
Outside Console
Guard owns its verdicts. Forge owns its product proposals. Console presents verified projections and customer-controlled review surfaces.
Consume pinned producer evidence and fail closed on mismatch.
Bind displayed material to its source digest and revision.
Search findings, planning outputs and lifecycle context.
Surface materiality and review context without assuming authority.
Produce bounded traceability manifests while retaining source history.
DESIGN DECISIONS
Imported material remains bound to producer revision and digest so the workbench cannot silently substitute different evidence.
Guard remains responsible for Guard verdicts. Forge remains responsible for Forge product proposals. Console consumes their contracts.
The workbench can surface materiality, notes and review context without inventing hidden priority or decision rights.
Bounded manifests can be exported while retaining the original source history and evidence lineage.
The point of Console is to make governed evidence easier for people to understand without allowing presentation logic to become approval, provisioning or reconciliation authority.
CURRENT MATURITY
The current Console baseline remains pre-1.0 and under CONTINUE_VALIDATION. Live adapters, customer-data processing, provisioning, lifecycle decisions and commercial activation remain separately governed.