Public packet playground
This page renders a fictional governed packet through the real packet view. It shows the verdict, missing proof, safe next action, human follow-through, and trust boundary before any live provider, private repo, database, secret, customer code, or operational material is involved.
Fixture proof limit
The data below is invented for local browser QA. It must not be used to infer live database behavior, provider behavior, customer security posture, merge approval, deployment approval, certification, or compliance status.
Public sample
The public sample explains the same verdict discipline in buyer-safe language before this full fixture view.
Open Public sampleHistory
History is the repeated-use surface for packet records, prior risks, resolved items, and human follow-through.
Open HistorySettings
Settings explains repo setup, export status, webhook status, packet sharing, and what is still gated.
Open SettingsCodaegis
Packet, verdict, missing proof, human note state, receiver limits, and transport are rendered as one bounded review surface.
Evidence entering packet
Source scope
example-org/example-service · PR #42
External checks
Checks visible; not decisive.
Missing proof
Focused test output is not attached.
Human note
Human decision: Unresolved
Verdict block
Verdict: Review
Review remains active; proof and human judgment stay separate.
REVIEW: proof is useful but still missing for the changed validation branch
Confidence meter
Confidence: 3/5 Moderate
Packet confidence label mapped for review display; it is not approval.
Missing proof
Focused test output is not attached.
Next action
Human decision owner requests the missing proof or records a decision to continue reviewing.
Human decision state
Human decision: Unresolved
Human decision remains separate from the packet verdict.
No actor recorded on this packet. No human note timestamp is recorded.
Receiver limits
Local synthetic fixture for UI QA only; not a real governed packet and not product authority.
Human
Can use for: Read verdict, proof, and human-note state.
Boundary: Human decision remains separate.
Agent
Can use for: Summarize packet context and missing proof.
Boundary: No autonomous action.
CI
Can use for: Inspect packet context and proof gaps.
Boundary: No merge, deploy, or writeback.
Internal Tool
Can use for: Show read-only packet detail.
Boundary: No command authority.
Private API read
Can use for: Read packet_detail:read fields.
Boundary: No unlock or write permission.
Webhook/export
Can use for: Carry same-packet detail.
Boundary: No second packet or authority transfer.
Can use for
Must not infer
Generated from fields
Fictional repo, fictional PR, and fictional review evidence. · Committed governed-packet rendering surface.
Same-packet transport
Browser view
Current packet viewThis page is the inspectable packet surface.
Private packet JSON
Not available herePacket JSON becomes available when this same governed packet exists and access allows it.
Export
Not available hereExport carries this packet detail only when settings and scope allow it.
Webhook/export
Not available hereWebhook/export surfaces carry this packet detail without adding authority.
Public API: Held
Private read scope can expose packet_detail:read only; no writes, runs, disposition writes, or public launch are added here.
Same packet
Continuity strip only; it is not progress, completion, or clearance.
Captured
Source scope preserved.
Checks visible
External checks stay subordinate.
Packaged
Evidence is packet-bound.
Governed now
Verdict and proof are visible.
Receiver scoped
Consumers stay bounded.
Packet available
Read and inspect only.
Held authority
Must not infer approval, merge, deploy, writeback, certification, clearance, or final authority.
Human decision remains separate; receivers get bounded packet context only.
This fictional governed packet keeps one pull request in REVIEW because the changed validation branch has a clear next step, but the governed packet does not contain enough proof for a human to treat it as in scope for a recorded path.
Review means useful work; proof is not ready yet.
This governed packet is decision support you can check now and return to later. It is saved to preserve the requested saved packet record and keeps the same pull-request scope visible across the browser, JSON, export, and webhook delivery. If the packet says proof is missing, use the safe next action before moving on.
Analysis source is missing verification for this saved packet record.
Synthetic local fixture only. This governed packet is fictional and was not produced by a live provider, database, real repository, or trusted analysis service.
Treat this as historical context, not as a current trusted-packet standard.
Governed packet
Codaegis supports the decision and records uncertainty. It does not become the decision-maker.
Trust limit
Synthetic local fixture only. This governed packet is fictional and was not produced by a live provider, database, real repository, or trusted analysis service.
Built to reduce unnecessary client-IP exposure; broader access should stay explicit, justified by the saved packet record, and authorized by the responsible human decision.
Client materials in this saved packet record support the requested check purpose, not hidden training, resale, profiling, or unrelated datasets.
Governed packet sharing
Delivery and navigation stay in the signed-in governed packet view. They do not create a second packet or a richer decision story than the saved packet record itself.
No JSON, export, or webhook link here can create a substitute packet.
Packet at a glance
The verdict, risk overview, and stakeholder summary all point to one governed packet. They make the same decision easier to discuss without creating a second packet story.
Decision summary
Review means useful work; proof is not ready yet.
Risk overview
Missing proof for changed validation branch
A decision owner can understand the risk, but should not treat the change as in scope for a recorded path until the missing proof is supplied.
This risk overview is a reading aid for this saved packet record only; it does not widen scope or approve action.
Stakeholder summary
Decision
REVIEW
REVIEW: proof is useful but still missing for the changed validation branch
Why it matters
Missing proof for changed validation branch
A decision owner can understand the risk, but should not treat the change as in scope for a recorded path until the missing proof is supplied.
What is missing
Focused test output is not attached.
Attach focused test output for the changed validation branch.
Next owner action
Human decision owner requests the missing proof or records a decision to continue reviewing.
The human decision owner still records the final disposition.
Review hand-off
Attach focused test output for the changed validation branch.
Fictional PR #42 changes one validation path in example-org/example-service.
Safe next action sequence
Use this as the short handoff from reading to action: fix what is missing, keep the safe state visible, then record the human disposition only when the human decision is real.
Safe state
Keep the change in review. Do not merge, deploy, or treat this fixture as live proof.
Access status: read-only PR-scoped fixture is enough for this governed packet.
Rollback and human decision
No rollback action is implied by this fixture; it is only a local QA surface for governed-packet detail rendering.
Human disposition state: still open; Codaegis supports the decision, but a responsible human still needs to record a disposition.
Packet navigation
This view is the saved record for example-org/example-service and PR #42, pinned to one governed packet.
Current view
Saved run record
You are reading the durable record, not only the newest result page.
Record anchor
PR #42
Run run_fixture_review_001 and packet pkt_fixture_review_001 stay aligned as one governed record.
Packet API JSON
Not available here
Packet retrieval becomes available once a governed packet exists and access allows it.
Risk findings
1
Findings stay bound to the saved packet record and remain the strongest decision pressure on this route.
Missing proof / fixes
2
Missing proof and fixes stay explicit so the human decision owner can move from packet to remediation without guessing.
Safe next actions
2
Human-directed next steps are rendered directly from the saved packet.
Latest delivery
No delivery sent
Delivery status stays attached to this same saved packet record, even when delivery needs setup or is not available here.
What Codaegis checked
These packet anchors describe the concrete pull request scope behind this saved packet record.
Why this verdict happened
Each finding stays tied to the workflow scope so you can inspect the same change in GitHub without exposing private scoring or routing traces.
The fictional pull request changes validation behavior, but no focused test output is attached to the governed packet.
A decision owner can understand the risk, but should not treat the change as in scope for a recorded path until the missing proof is supplied.
Evidence anchor · Fictional PR #42 · changed area: request validation · evidence class: written summary only
Access and client-IP boundary
Proof limit: permission needs stay explicit so Codaegis can limit unnecessary client-IP exposure while showing whether more access would materially improve this saved packet record.
Missing proof and required fixes
These are the smallest recorded proof gaps or fixes needed before this governed packet becomes more trustworthy.
Safe next action
These are the immediate human-directed follow-through steps after reading the saved packet record.
What remains uncertain
Codaegis keeps missing proof and uncertainty visible so the saved packet record does not overclaim confidence.
Keep the change in review. Do not merge, deploy, or treat this fixture as live proof.
No rollback action is implied by this fixture; it is only a local QA surface for governed-packet detail rendering.
Human follow-through
Recording a human decision for this governed packet still sets the next comparison point, even though no prior saved packet is available for this repo.
Current human decision
Human decision: UnresolvedThis is the current human follow-through state for the saved packet record. Browser, export, JSON, and webhook surfaces all carry this same current governed packet state. Codaegis supports the decision; it does not become the decision-maker.
This governed packet is still open. Decide whether to record the current human path, record a different path, or leave it open until the missing proof is handled.
Decision actor
No decision actor recorded yet
Recorded
Not recorded
Disagreement history
Private to this repoThe saved packet record carries the current recorded human note, decision actor alias, timestamp, and different-path reason when present. The full disagreement record stays private to this repo.
Human disposition override ledger
One current governed packet stateThis ledger is the compact human-decision trail for the packet. It keeps the recorded, open, or different-path state attached to the same saved packet record so History does not have to guess what happened later.
Saved packet record created
May 9, 2026, 6:00 PM
Packet pkt_fixture_review_001 was saved for example-org/example-service PR #42.
Current disposition
Human decision: Unresolved
This governed packet is still open. Decide whether to record the current human path, record a different path, or leave it open until the missing proof is handled.
Decision actor
No decision actor recorded yet
No human disposition timestamp is recorded yet.
Different-path reason
Not recorded
A reason is required only when the human decision owner chooses a different path.
Packet transport sharing
These links and delivery states carry this same governed packet without approving it, changing it, or creating new authority.
Governed packet JSON
Not available herePacket API JSON becomes available once this same governed packet exists and access allows it.
Packet export
Not available herePacket export becomes available when settings and packet state both allow it. It shares this packet; it does not approve, change, or replace it.
Webhook delivery
Not available hereWebhook delivery becomes relevant once the repo has a destination and a governed packet. Delivery carries this packet; it does not create a new one or add authority.
No webhook destination configured
Packet transport receiver limits
Packet API, export, and webhook delivery carry this same governed packet; they do not create merge, writeback, approval, live, public-readiness, or enforcement authority.
Receiver limits
Local synthetic fixture for UI QA only; not a real governed packet and not product authority.
Can use for
Must not infer
Saved packet record and attestation
This is the durable record metadata behind the saved packet record and its packet attestation.