CorWeen AI — The Human-Controlled Execution Firewall for AI Agents

Kiroween 2026 work-in-progress draft — NOT SUBMITTED. Proposed category: Frankenstein.

Problem

AI agents can propose useful actions, but a successful tool call alone does not ensure that the action was authorized, precisely reviewed, or safe to repeat. CorWeen AI explores an execution boundary between agent proposals and changes to protected records.

What works today: synthetic, localhost-only Judge Lab

The downloadable Windows prototype (publication pending) runs a real Python HTTP reviewer and SQLite record/audit engine at http://127.0.0.1:8766/lab on the local machine.

  1. Propose: create an exact change contract for synthetic record DEMO-CARE-001.
  2. Block: a pre-approval execution attempt is rejected without changing the record.
  3. Approve: inspect the exact action and approve it using a session-only local demo token.
  4. Execute once: the execution gateway rechecks the contract and updates the synthetic SQLite record.
  5. Reject replay: repeating the same action is blocked; local audit history records the events.

Verification evidence (local, not Kiro-native)

  • 146/146 Python unit tests passed on the extracted Windows Judge Test Build.
  • 10/10 subprocess + live HTTP smoke checks passed, including blocked pre-approval execution, version stability before approval, execution exactly once, replay rejection, and SQLite audit events.
  • The verification used a temporary database and did not record the randomized approval token.
  • Independent Audit Timeline event-filter acceptance tests remain 2/8 PASS, 6 FAIL, by design: the missing event filter is reserved as a real Kiro Spec-to-Code task.

Architecture and limits

Python, SQLite, MCP-facing adapter, action-bound proposal/approval/execution checks, local audit chain, and an HTML reviewer. No real patient, veterinary, commercial, or production records are accessed. The demo token is not verified human identity; the local hash chain is not externally immutable. Do not expose the localhost reviewer directly to the public internet. A separate static web illustration is only a simulation and does not execute backend actions.

Kiro development and eligibility — PENDING

A .kiro/ specification, Steering, Hook, and MCP configuration exist in the source, but configuration is not proof of genuine Kiro IDE usage. Native Kiro code changes, PostFileSave trigger receipts, and MCP invocations have not yet been independently verified. Do not mark the main Kiro technology requirement complete.

Some managed-record, MCP, and other components are inherited/adapted from prior CoAi engineering prototypes. The provenance ledger and comparisons disclose this inheritance; first-creation dates and eligibility under the Kiroween 2026 New Projects Only rule remain unresolved. An organizer clarification email has been prepared but not sent. The presence of a disclosure field is not an organizer ruling.

Publication / submission status

  • Full public GitHub source repository: not yet created.
  • Public Judge Test Build download URL: not yet published.
  • Public demo video under three minutes: not yet published.
  • Devpost submission: draft only; not submitted.

Next gates: obtain eligibility clarification, gather authentic Kiro implementation evidence, publish independently reviewed source and judge test build, record a truthful demonstration video, and verify the official submission fields.

Built With

Share this project:

Updates