decisionThe Codices

0014 — Public ecosystem and pathway architecture

A recorded institutional decision, with reasoning and result.

Authority rank
5
Version
v1.0
Adopted
unrecorded
Held by
Stewardship Office
System
SYS-10

Source · docs/codices/DECISIONS/0014-public-ecosystem-and-pathway-architecture.md · registered by rule

  • Date: 2026-09-18
  • State: accepted
  • Authority: Codex 1 Arts. II–VI; Codex 0 §§07, 11, 20, 21; Codices 6, 8, 10; STD-X, STD-Q
  • System: SYS-06 Ventures for the ecosystem record; SYS-04 Business for public pathways; SYS-09 Analytics for reporting integrity

Decision

Anabasis will publish five paths into its work—Academy, Accelerator, Venture Development, Strategic Advisory, and Institutional Programmes—from one shared source. Research, Technology, and proprietary investment remain operating activities, but are not represented as additional application pathways.

The Ecosystem and Institutions surfaces will publish the supplied institutional architecture rather than the former speculative concept records. The commercial register names Anabasis, Synarch, AXION, PHYLAX, HuHos.io, NexEstate, ResTerra, APODEMOS, HELM, Atherion Wellness, and Promachos. KOINONIA is shown separately as a structurally independent public-benefit institution, with OIKODOME and ANORTHOSIS nested beneath it as initiatives.

Inclusion establishes no ownership, control, investment, collaboration, operation, endorsement, or legal affiliation. Missing facts stay absent.

Registry readiness — ENT-38 Public Ecosystem Record

  1. 1What it is: the administrator-approved editorial record of names, structural classification, and nested initiatives shown publicly.
  2. 2Why it exists: strengthens trust and community by preventing unsupported relationship claims while making the architecture legible.
  3. 3Who uses it: public visitors, institutional counterparties, and the Executive and Ventures offices.
  4. 4How it connects: consumed by SURF-07 and SURF-08; later superseded by canonical Organization and Venture records (ENT-03/15) through API-08.
  5. 5What governs it: Codex 0 §§07, 11, 20; Codex 5; Codex 6; STD-D and STD-Q.
  6. 6Owner: DIV-04 Ventures.
  7. 7Data consumed and produced: consumes administrator-approved names and structural classifications; produces no legal, financial, or operating fact.
  8. 8Future dependents: the venture pipeline, relationship verification, and future public reporting may reference its successor canonical records.

It does not duplicate ENT-03 or ENT-15: those remain the future canonical organization and venture entities. At one hundred times the scale, editorial records would fail through manual verification load and are replaced by those entities and a governed publication workflow. ENT-38 therefore remains partial.

Institutional Critic

  1. 1Scale: manual relationship review fails first. A governed Organization record and publication workflow replace this editorial source before scale.
  2. 2Assumptions: the supplied names and KOINONIA hierarchy are approved for publication; legal relationships, websites, operating status, and missions remain unverified and therefore absent.
  3. 3Simpler solution: replacing the names without changing the model would preserve unsupported charter and case-study fields. A small purpose-built record is the simpler safe solution.
  4. 4Duplication: public pathways reuse SURF-23; ecosystem routes reuse SURF-07/08. No surface, form, system, or intake is duplicated.
  5. 5Enterprise view: procurement users see explicit evidence boundaries and no implied partnership, contract, grant, or performance claim.
  6. 6First-time user: the five pathways appear immediately after the ascent; the ecosystem separates commercial and public-benefit structures before listing relationship terminology.
  7. 7Legal, operational, security: the material risk is false affiliation. Safe defaults and noindexed detail records constrain it. No personal data or new backend boundary is introduced.
  8. 8Debt: relationship verification remains editorial. DIV-04 owns repayment through ENT-03/15 and API-08 before the register becomes operational data.
  9. 9Consistency: the change advances Codex 1's capability mission, Codex 6's confidence standard, Codex 8's public/proprietary separation, and Codex 0 §20.6.4's Business/Ventures boundary.

Financial evaluation

  • Revenue potential: indirect; clearer selection of existing paid pathways.
  • Implementation cost: low; editorial and presentation work only.
  • Maintenance cost: low at current scale, rising with each verified record.
  • Operational complexity: administrator verification is the limiting factor.
  • Customer value: clearer entry and reduced affiliation ambiguity.
  • Enterprise value: safer diligence and procurement interpretation.
  • Long-term strategic value: a trustworthy precursor to canonical ecosystem records.

Result and review

Review date: 2027-03-18. Record whether visitors selected better-fit pathways, whether any relationship classification was challenged, and whether ENT-38 was replaced by canonical Organization and Venture records. The result is written whether or not it supports this decision.