{"id":47232424,"title":"Show HN: ODL – Organization as Code. I wrote specs, AI wrote 100% of the code","points":1,"user":"ku_","time":1772546432,"time_ago":"4 hours ago","type":"link","content":"

Hi HN,

For the past few months, I’ve been wrestling with a paradox: Individually, AI agents are incredibly fast. Yet, when deployed as a team, organizational throughput often stays flat. We end up acting as "Human Wrappers," manually marshaling data between probabilistic agents.

I decided to treat this as a systems problem, not a management problem. ODL (Organizational Definition Language) is an attempt to bring a "SQL Moment" to agent organizations. Instead of micromanaging how agents work, ODL lets you declare what the structure should be.

Here is a simplified example of an ODL definition orchestrating a self-correcting team with a human-in-the-loop gate:

  approval_gate:\n    target: ArchitectureSpec\n    approver: CTO\n    contents:\n      generate_team:\n        generator: LeadArchitectAgent\n        validators: [SecurityAuditor, PerformanceExpert]\n        loop: 3\n        inputs: ["BusinessRequirement", "SecurityStandard"]\n        output: ArchitectureSpec\n        briefing:\n          mission: "Design a zero-trust architecture for 10k RPS."\n

\nKEY ARCHITECTURAL PILLARS:

1. Functional Core / Imperative Shell: We run probabilistic AI on top of a pure, side-effect-free functional kernel (odl-kernel). It takes the current state (Snapshot) and an event, and calculates the exact next transition without hitting databases directly.

2. Deterministic Convergence: To ensure predictable execution of unpredictable agents, the kernel relies on a deterministic loop:

  for _ in range(self.MAX_ITERATIONS):\n      has_change = False\n      if self._step_a_transition(...): has_change = True\n      if self._step_b_expansion(...): has_change = True\n      if self._step_c_dispatch(...): has_change = True\n      if not has_change: break # Convergence reached\n

\n3. Deterministic Identity: Every node and event is assigned absolute "Space-Time Coordinates" using deterministic UUID v5 generation based on its structural path. Past iterations crystallize into an addressable, immutable history, making the system replayable.

THE "CORTEX" EXPERIMENT:

I am a systems architect/PM by trade. In fact, I have absolutely zero Python programming knowledge. To test my thesis that "if the architecture is rigorous enough, execution becomes purely computable," I spent 40 days defining the core principles and designing over 50 architectural proof patterns (Source-to-IR transformations) in YAML.

I treated the YAML test cases as the absolute law; the AI implementation was rejected repeatedly until it achieved 100% coverage and passed all 50+ structural proof patterns.

I functioned purely as the "Cortex" — defining the Why and the What — while forcing the AI to figure out the How. The result is a fully functional, deterministic Python kernel that passes 100% of its tests. It serves as a physical, verifiable manifestation of the ODL spec.

REPOS:

- L1 (odl-lang) Compiler: https://github.com/co-crea/odl-lang (Apache 2.0)

- L0 (odl-kernel) Execution Engine: https://github.com/co-crea/odl-kernel (BSL 1.1 - Ensuring sustainability for the infrastructure while keeping the language open)

This project is dedicated to the memory of my mentor, Prof. Kazuhisa Seta. He taught me that "structure is the essence of intelligence."

I'd love to hear your thoughts on the architecture, the UUID approach, or the concept of defining organizations as code!","url":"item?id=47232424","comments":[{"id":47232434,"level":0,"user":"ku_","time":1772546459,"time_ago":"4 hours ago","content":"

[dead]","dead":true,"comments":[]}],"comments_count":1}