Mission-grade intelligence systems for the organizations operating Latin America.

Sistemas de inteligencia de misión crítica para las organizaciones que operan Latinoamérica.

ARKELYTHEX builds the Drenyra Accounting Ecosystem: a verifiable financial operating system where fiscal correctness, tenant isolation, and auditability are product safety requirements. Web, CLI, agents, and memory share one discipline — receipts prove execution, contracts freeze behavior, and a human accountant remains the final authority.

The core is six repositories with strict, explicit boundaries:

```text
                        ┌───────────────────────┐
                        │ Drenyra-Engram        │  Institutional memory
                        └───────────▲───────────┘  (informs, never authorizes)
                                    │
                   ┌────────────────┴────────────────┐
                   │                                 │
          ┌────────┴────────┐              ┌──────────┴─────────┐
          │ Drenyra-AI      │              │ Drenyra-Pi         │  Pi-native
          │ Verifiable core │◄─────────────│ (pins drenyra-ai)  │  harness
          └───────▲─────────┘              └────────────────────┘
                  │
          ┌───────┴─────────┐
          │ Drenyra Command │  Command Center — web + API + TUI
          │ Center          │  (consumes drenyra-ai contracts)
          └─────────────────┘

  Drenyra-Skills          → versioned accounting/tax knowledge (content layer)
  Drenyra-Guardian-Angel  → independent adversarial verification (consumes contracts)
```

• drenyra-command-center consumes released, versioned drenyra-ai; uses drenyra-engram for context.
• drenyra-pi consumes a pinned, package-local, checksum-verified drenyra-ai (never PATH); uses drenyra-engram.
• drenyra-ai never depends on the Command Center or Pi, and never knows Drenyra Pi exists.
• drenyra-engram is independent — it informs, it never authorizes.
• drenyra-skills is content (versioned knowledge), not code — the drenyra-ai runtime validates and agents consume it.
• drenyra-guardian-angel verifies against the frozen drenyra-ai contracts — never the author of what it reviews.

Drenyra database           → transactional truth
Drenyra Engram             → institutional memory (guides, never authorizes)
Drenyra AI receipts+ledger  → execution proof (Ed25519-signed, append-only)
Drenyra Guardian Angel     → independent adversarial verification (never the author)
Drenyra Pi                 → operator experience
Human accountant           → final authority

• Mission-grade — idempotent operations, total traceability, graceful degradation.
• Evidence-native — every action produces verifiable evidence automatically (RDA receipts, audit ledger).
• Human command — AI assists and prepares; humans authorize (R2 single, R3 dual approval); systems execute.
• Deterministic fiscal truth — fiscal paths are test-covered; money is integer math (BigInt cents), never floats.
• Scope-first — company/RUC/period isolation is structural in queries, memory, and search.
• Contracts as public surface — versioned, transport-agnostic, with canonical vectors and migration paths.

Future verticals (industrial operations, public sector, edge) are planned but have no public repositories yet — they will land as clearly-identified repos, never mixed into drenyra-command-center.

1. Drenyra AI industrialization — finish gates + recovery, freeze first contracts (0.1.0), release with provenance (SHA-256 manifest, SBOM, signed tag).
2. Drenyra Pi harness — packed verification, private Drenyra AI installer, /drenyra:status + /drenyra:doctor end-to-end.
3. Drenyra Engram engine — freeze strategy (neutral contracts, in-memory reference, PostgreSQL authority), build + packaging.
4. Drenyra scope discipline — no new non-accounting verticals enter the product repo; progressive retirement of foreign folders.

The six Drenyra repositories define the current production architecture. Some production repositories may remain private while public contracts, specifications, threat models, and reference slices are released progressively. Everything else on this page is auxiliary or in transition.