A-FORGE

Execute only what has been authorized.

The governed execution shell of the arifOS Federation.

A-FORGE is the hands. It executes. It never judges. It never self-authorizes.

DITEMPA BUKAN DIBERI — Forged, Not Given.

---

Why A-FORGE exists

Three questions govern every action:

1. Who performs the action?
2. Who approved the action?
3. Who witnessed the action?

A-FORGE answers only the first.

Approval belongs to arifOS. Authority belongs to the sovereign. Receipts belong to VAULT999.

What you get

Input:
SEAL + lease + session

Output:
Execution + receipt

What A-FORGE does NOT do

A-FORGE is not a judge. A-FORGE is not a policy engine. A-FORGE does not emit SEAL. A-FORGE does not emit HOLD. A-FORGE never certifies its own execution.

30-second proof

Request: "delete production database"
  Without SEAL        → HOLD

Request: "deploy approved release"
  With SEAL + lease   → Execute
                     → Receipt
                     → VAULT999

Architecture in one sentence

The executor never certifies its own work.

flowchart LR
    Intent[Intent] --> Judge[arifOS]
    Judge -->|SEAL| Forge[A-FORGE]
    Forge --> Receipt[Receipt]
    Receipt --> Vault[VAULT999]
    Judge -->|HOLD| Human[Human Review]

Loading

Federation card

ARIF = Sovereign · arifOS = Law · AAA = Institution · A-FORGE = Hands

ARIF vetoes. arifOS judges. AAA routes. A-FORGE executes.

Full technical README: docs/README-FULL.md · MCP door: forge.arif-fazil.com/mcp