Current scoped path
Open signed-in session
Codaegis still needs a truthful signed-in account before any repo, run, or settings can compound.
Workspace governance
Read current scope, one active repo, and packet continuity.
Home shows your signed-in account, current repo, latest governed packet, and best next scoped path in one place. The loop stays simple on purpose: Home, Connect, Run, then return here or History after a governed packet is saved.
Account
No signed-in accountMissing: sign-in. Codaegis will not guess which account owns the next check; use Connect to resolve identity first.
Current repo
No repoMissing: connected repo. Connect one repo before checks, governed packets, and repeated use can safely build up.
Latest governed packet
No governed packetMissing: a packet-producing check with a governed packet. Start with Connect, then Run.
Saved setup
No governed packetMissing: first governed packet. Run one checked PR before comparing current repo setup.
Since prior packet
No comparisonMissing: prior governed packet. History needs at least one past governed packet before comparison can help.
Packet transport scope
No packet transport recordNo governed packet transport records exist yet for the current repo.
If the loop stops
Codaegis names the hold before it asks you to continue.
Early checks can stop because identity, repo access, a PR, trusted analysis, packet creation, or packet transport is outside the current scope. That is a protected state: Codaegis should explain the missing step instead of inventing a governed packet.
No signed-in account
Home and Connect show no account owner.
Sign in first so the next governed-packet check belongs to one accountable user.
No connected repo or PR
Connect or Run says repo access, one repo, or one pull request is missing.
Return to Connect, make one repo explicit, then choose one listed PR in Run.
Trusted analysis needs setup
Run is paused or Result has no verified governed packet.
Check Settings or retry Run after setup; Codaegis stays empty instead of inventing a substitute packet.
Packet transport needs attention
History or Home shows packet transport gated, failed, skipped, or unavailable.
Open the saved packet or Settings; packet transport scope never creates a new verdict or approval.
Needs follow-up
Keep repeated use clear by showing which governed packets still need follow-up.
This queue keeps governed packets still open and transport issues visible from Home so the next step stays explicit instead of disappearing into memory.
Queued governed packets
0
Saved governed packets still open or waiting on packet transport follow-through.
Repo impact
0
Distinct repos currently represented in the follow-up queue.
Hard stops
0
Saved governed packets that currently hold continuation without a human note.
Transport needs attention
0
Saved governed packets whose packet transport record needs attention.
No governed packet currently needs follow-up.
No queue item is asking for attention right now: no open governed packet, unresolved stop verdict, or packet transport record needs immediate attention. Use Run for the next pull request that needs a check or History if you want to compare prior packets.
Recent governed packets
Open a recent governed packet or its full record.
The three most recent governed packets, for quick return. History keeps the full, filterable list.
No governed packets yet.
Once the first scoped PR check saves a governed packet, the most recent ones appear here for quick return.
See an example
Preview a sample governed packet before connecting a repo.
A fixed sample governed packet shows what a packet-producing check looks like — verdict, evidence, and next actions — without signing in or running anything.