RE:ENTRY is a human-governed AI recovery agent for the worst paperwork days of your life. After a flood, eviction, or similar crisis, one person may have to reconcile county notices, leases, photos, insurer emails, repair estimates, and utility deadlines at once. The work is repetitive, but the consequences are not: a wrong amount, an unverified address, or an unreviewed message can delay housing or create a new problem.
RE:ENTRY turns a recovery case into an inspectable evidence graph and action queue. A Strands Agent proposes a bounded recovery plan from the case snapshot, attaches citations to source records, flags contradictions instead of guessing, and labels actions by risk. Deterministic policy code remains the authority for side effects. Actions that share personal information or create an official case pause at a human checkpoint; a reviewer sees the citations, records a decision note, and approves one action against the case revision they inspected.
The demo starts with synthetic Flood recovery / Case 042 data: six evidence records, a $4,680 versus $5,140 conflict, and a housing packet awaiting approval. Approval produces a deterministic mock receipt. A simulated insurer rejection becomes new evidence, and RE:ENTRY adds a cited signed-inventory follow-up behind a new approval checkpoint. Uploads are bounded, signature-checked, hashed, and quarantined for review. No real resident, agency, insurer, bank, or utility is contacted.
The demo uses a deterministic offline Strands model so it runs without AWS credentials. REENTRY_MODE=live switches the same planning boundary to Strands BedrockModel with explicit region/model allowlists, bounded turns and token budgets, and default minimization of unreviewed evidence and direct identifiers. The repository includes an AgentCore HTTP runtime specification and deployment preflight, but no AWS deployment is claimed yet. Setup, testing instructions, architecture documentation, and an MIT license are included in the public repository. Verified local checks: 59 backend tests passed and the Vite production build passed.
Log in or sign up for Devpost to join the conversation.