What AFFE Does
AFFE is the funding normalization and appropriation fidelity layer of A.B.E.
It helps turn messy funding documents into structured artifacts, then evaluates whether funding, appropriation purpose, scope conditions, and deployment remain aligned.
Plain language: Did the funding stay connected to the purpose it was allocated for?
Two Jobs, One Module
AFFE can support CSV, spreadsheet, PDF, text, or structured funding inputs and convert them into analysis-ready artifacts.
AFFE reads RT, CII, Integration, and CFF outputs to evaluate funding fidelity and post-deployment stability.
Run AFFE Stability / Fidelity Check
Waiting.
Plain-Language Result
Key AFFE Values
Funding Document Normalization
This section is the front door for AFFE’s original role: turning funding documents into structured artifacts. Full parser wiring can be expanded later; this page preserves the interface and local-only intent.
Supported targets: CSV, TXT, JSON, PDF, XLSX/XLS.
No funding artifact built yet.
Required Funding Fields
| Field | Plain Meaning |
|---|---|
program_name | Name of the program or funding stream. |
federal_authority_citation | USC, CFR, grant, or authority connected to the funding. |
fiscal_year | Year the funding applies to. |
state_or_jurisdiction | State, county, agency area, or jurisdiction. |
agency | Agency receiving or administering the funds. |
line_item_description | Description of the spending line. |
spend_category_code | ON_MISSION, OFF_MISSION, or UNCLEAR. |
amount_usd | Dollar amount. |
notes | Optional context. |
Trace
| Required Input | Status |
|---|---|
| No run yet. | |
Advanced AFFE JSON
—
Local Funding Artifact JSON
—