Skip to content

Mission R follow-up: fix README DAG label + delete stale vault-readiness report #12

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
Gio2050 merged 1 commit into from
Jul 19, 2026
Merged

Mission R follow-up: fix README DAG label + delete stale vault-readiness report #12

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -91,7 +91,7 @@ package name and no hardcoded Institute tenant identity.

`afi-gateway` runs on **ElizaOS** (`@elizaos/core`). Its upstream dependency tree resolves additional third-party packages into `package-lock.json` that AFI does not import, configure, or build on. Those are upstream vendor metadata, not part of AFI's architecture.

AFI's orchestration is the deterministic DAG pipeline in **`afi-reactor`**; signal scoring, validation, and minting source of truth remain **`afi-reactor`**, **`afi-core`**, and **`afi-config`** — not this gateway.
AFI's orchestration is the manifest-driven pipeline runtime in **`afi-reactor`**; signal scoring, validation, and minting source of truth remain **`afi-reactor`**, **`afi-core`**, and **`afi-config`** — not this gateway.

See [`afi-docs/ARCHITECTURE_STATUS.md`](https://github.com/AFI-Protocol/afi-docs/blob/main/ARCHITECTURE_STATUS.md) for the architecture summary.

Expand Down
Loading
Loading