Skip to content

add NFATs to content overview + fix diagram alignment #1

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

Open
nikozalo wants to merge 3 commits into
base: main
Choose a base branch
from
Open

add NFATs to content overview + fix diagram alignment #1

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e5d82cd
chore: add NFATs to contents
nikozalo Jan 22, 2026
73f980b
fix: diagram alignments
nikozalo Jan 22, 2026
9439c10
fix: alignment of diagram
nikozalo Jan 22, 2026
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
1 change: 1 addition & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -67,6 +67,7 @@ Laniakea smart contract architecture built on the **PAU pattern** (Parallelized
| architecture-overview.md | Four-layer capital flow (Generator → Prime → Halo → RWA), PAU pattern, modular design |
| configurator-unit.md | Governance layer: BEAM hierarchy (aBEAM/cBEAM/pBEAM), rate limits, SORL |
| lcts.md | Liquidity Constrained Token Standard — queue-based tokens for fair capacity distribution |
| nfats.md | Non-Fungible Allocation Token Standard — bespoke capital deployment deals with individual terms |

### governance-operations/
Governance structure and autonomous operational infrastructure.
Expand Down
66 changes: 33 additions & 33 deletions governance-operations/atlas-synome-separation.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -167,51 +167,51 @@ The existing Atlas hierarchy already hints at the split:

```
┌─────────────────────────────────────────────────────────────────────┐
│ SYNOME │
│ (Graph database - all operational data) │
│ │
│ SYNOME │
│ (Graph database - all operational data) │
│ │
│ ┌───────────────────────────────────────────────────────────────┐ │
│ │ ATLAS │ │
│ │ (Root node - human-readable constitution) │ │
│ │ │ │
│ │ A.0 Spirit of the Atlas │ │
│ │ A.1 Governance (who decides, how) │ │
│ │ A.2 Primitives (what building blocks exist) │ │
│ │ A.3 Risk Framework (seniority, encumbrance principles) │ │
│ │ A.4 Protocol (tokens, rewards, BEAM pattern) │ │
│ │ A.5 Accessibility (compliance philosophy) │ │
│ │ ATLAS │ │
│ │ (Root node - human-readable constitution) │ │
│ │ │ │
│ │ A.0 Spirit of the Atlas │ │
│ │ A.1 Governance (who decides, how) │ │
│ │ A.2 Primitives (what building blocks exist) │ │
│ │ A.3 Risk Framework (seniority, encumbrance principles) │ │
│ │ A.4 Protocol (tokens, rewards, BEAM pattern) │ │
│ │ A.5 Accessibility (compliance philosophy) │ │
│ │ A.6 Agent Types (what Primes and Executors are) │ │
│ └───────────────────────────────────────────────────────────────┘ │
│ │ │
│ │ │
│ ┌──────────────────┼──────────────────┐ │
│ ▼ ▼ ▼ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Spark Agent │ │ Grove Agent │ │ Keel Agent │ ... │
│ │ Artifact │ │ Artifact │ │ Artifact │ │
│ ├──────────────┤ ├──────────────┤ ├──────────────┤ │
│ │ SubProxy │ │ SubProxy │ │ SubProxy │ │
│ │ Rate Limits │ │ Rate Limits │ │ Rate Limits │ │
│ │ Instances[] │ │ Instances[] │ │ Instances[] │ │
│ │ ICDs[] │ │ ICDs[] │ │ ICDs[] │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ ┌──────────────┐ ┌──────────────┐ ┌──────────────┐ │
│ │ Spark Agent │ │ Grove Agent │ │ Keel Agent │ ... │
│ │ Artifact │ │ Artifact │ │ Artifact │ │
│ ├──────────────┤ ├──────────────┤ ├──────────────┤ │
│ │ SubProxy │ │ SubProxy │ │ SubProxy │ │
│ │ Rate Limits │ │ Rate Limits │ │ Rate Limits │ │
│ │ Instances[] │ │ Instances[] │ │ Instances[] │ │
│ │ ICDs[] │ │ ICDs[] │ │ ICDs[] │ │
│ └──────────────┘ └──────────────┘ └──────────────┘ │
│ │ │ │ │
│ ▼ ▼ ▼ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ ┌───────────────────────────────────────────────────────────────┐ │
│ │ Instance Nodes │ │
│ │ Morpho USDS, Aave USDC, Curve USDS-USDC, Treasury Bills... │ │
│ │ Each with: addresses, rate limits, operational procedures │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ │ Morpho USDS, Aave USDC, Curve USDS-USDC, Treasury Bills... │ │
│ │ Each with: addresses, rate limits, operational procedures │ │
│ └───────────────────────────────────────────────────────────────┘ │
│ │
│ ┌───────────────────────────────────────────────────────────────┐ │
│ │ Config Nodes │ │
│ │ BEAM parameters, Penalty schedules, Settlement formulas │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ ┌──────────────────────────────────────────────────────────────┐ │
│ └───────────────────────────────────────────────────────────────┘ │
│ │
│ ┌───────────────────────────────────────────────────────────────┐ │
│ │ Transaction Logs │ │
│ │ All Sentinel actions, settlements, state changes, precedents │ │
│ └──────────────────────────────────────────────────────────────┘ │
│ │
│ └───────────────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────────────────┘
```

Expand Down
12 changes: 6 additions & 6 deletions legal-and-trading/identity-network.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -229,18 +229,18 @@ Token Configuration (set by issuer):
Each Identity Network controls a legal entity that performs actual KYC:

```
┌─────────────────────────────────────────────────────────┐
┌──────────────────────────────────────────────────────────┐
│ Identity Network Halo │
│ (On-chain governance) │
│ │
│ ┌────────────────────────────────────────────────────┐ │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ Identity Registry │ │
│ │ (On-chain: simple address list) │ │
│ └────────────────────────────────────────────────────┘ │
│ └─────────────────────────────────────────────────────┘ │
│ │ │
│ controls │
│ ▼ │
│ ┌────────────────────────────────────────────────────┐ │
│ ┌─────────────────────────────────────────────────────┐ │
│ │ Legal Entity │ │
│ │ (Foundation, LLC, or regulated entity) │ │
│ │ │ │
Expand All @@ -249,9 +249,9 @@ Each Identity Network controls a legal entity that performs actual KYC:
│ │ - Stores records (off-chain) │ │
│ │ - Updates Synome → stl-identity syncs to chain │ │
│ │ - Handles disputes, appeals, revocations │ │
│ └────────────────────────────────────────────────────┘ │
│ └─────────────────────────────────────────────────────┘ │
│ │
└─────────────────────────────────────────────────────────┘
└──────────────────────────────────────────────────────────┘
```

### KYC Processing Flow
Expand Down
20 changes: 10 additions & 10 deletions legal-and-trading/passthrough-halo.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,17 +74,17 @@ This creates a flywheel where established Passthrough Halos become increasingly

```
┌─────────────────────────────────────────────────────────────────────┐
│ SKY PROTOCOL │
│ │
│ SKY PROTOCOL │
│ │
│ ┌─────────────┐ │
│ │ Primes │ Capital allocation entities within Sky │
│ └──────┬──────┘ │
│ │ │
│ │ Deploy capital via standardized vaults │
│ ▼ │
│ ┌─────────────────────────────────────────────────────────────┐ │
│ │ PASSTHROUGH HALO │ │
│ │ │ │
│ │ PASSTHROUGH HALO │ │
│ │ │ │
│ │ ┌───────────────┐ ┌───────────────┐ ┌───────────────┐ │ │
│ │ │ Halo Unit A │ │ Halo Unit B │ │ Halo Unit C │ │ │
│ │ │ (e.g., CLO) │ │ (e.g., T-Bill)│ │ (e.g., MMF) │ │ │
Expand All @@ -96,9 +96,9 @@ This creates a flywheel where established Passthrough Halos become increasingly
│ │ │
▼ ▼ ▼
┌───────────────────────────────────────────────────────┐
│ ASSET MANAGEMENT PARTNERS │
│ │
│ CLO Manager T-Bill Provider Money Market Fund │
│ ASSET MANAGEMENT PARTNERS │
│ │
│ CLO Manager T-Bill Provider Money Market Fund │
└───────────────────────────────────────────────────────┘
```

Expand Down Expand Up @@ -241,7 +241,7 @@ This isn't a gradual ramp-up. It's immediate, coordinated capital deployment acr
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ 2. PREPARATION │
│ 2. PREPARATION │
│ • Asset manager confirms readiness and terms │
│ • Unit Sentinel configured for asset-specific requirements │
│ • Smart contracts prepared via Laniakea Factory │
Expand All @@ -250,15 +250,15 @@ This isn't a gradual ramp-up. It's immediate, coordinated capital deployment acr
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ 3. GOVERNANCE APPROVAL │
│ 3. GOVERNANCE APPROVAL │
│ • Halo Artifact Edit proposed with Unit specifications │
│ • Standard approval process (typically days, not weeks) │
│ • Smart contracts deployed from factory │
└─────────────────────────────────────────────────────────────────────┘
│
▼
┌─────────────────────────────────────────────────────────────────────┐
│ 4. LIVE — IMMEDIATE CAPITAL DEPLOYMENT │
│ 4. LIVE — IMMEDIATE CAPITAL DEPLOYMENT │
│ • All Primes automatically rebalance into new Unit │
│ • Potential for hundreds of millions in Day 1 inflows │
│ • Unit Sentinel processes deposits and manages positions │
Expand Down
Loading