{"slug": "show-hn-foundation-a-different-approach-to-software-and-ai", "title": "Show HN: Foundation, a different approach to software and AI", "summary": "Ovasabi Foundation, a full-stack application substrate for high-performance event-driven systems, has been released as an open-source toolkit. It offers tenant-isolated architecture, seven performance planes from nanosecond to microsecond, and built-in observability. The project targets teams that embrace managed infrastructure and performance optimization.", "body_md": "**A full-stack application substrate for high-performance, event-driven systems.**\n\nOvasabi Foundation is an integrated toolkit for teams that want to evolve code. It provides the platform modules, scaffolds, enforcement checks, and documentation to bootstrap and maintain production systems with:\n\n**Tenant-isolated, event-driven architecture**— every operation carries metadata: who asked, what organization, correlation ID** Performance ladder**— seven planes from nanosecond direct dispatch to microsecond JSON compatibility** Hermes hotplane**— bounded, node-local projections for sub-microsecond operational reads** Worker orchestration**— bounded background processing with retry policies and progress tracking** Built-in observability**— logs, metrics, and traces automatically linked by correlation ID\n\nNot a no-code platform. Not zero-DevOps. Not for teams that want to move fast by cutting corners. Foundation is for teams that embrace managed infrastructure, understand performance, and expect their codebase to evolve.\n\n| Component | Tech Stack | Purpose |\n|---|---|---|\nserver-kit |\nGo | Backend: event bus, workers, Hermes, database, resilience, observability |\nruntime-transport |\nTypeScript | Client wire: command bus, envelope creation, metadata stores, WebSocket/HTTP fallback |\nruntime-sdk |\nRust/WASM | High-performance kernel: 4KB control buffer, zero-copy communication |\nui-minimal |\nTypeScript/React | Shared UI primitives, semantic theme tokens, motion helpers |\nfrontend-kit |\nTypeScript | IndexedDB storage, metadata helpers, runtime adapters, transfer progress |\nruntime-native |\nTauri/Rust | Native shell bridge: secure storage, GPU handles, device access |\nconfig-contracts |\nGo/TypeScript | Cross-language configuration schemas |\n\n**Data Layer**: PostgreSQL (durable truth), Redis (coordination), Protocol Buffers (contracts), Cap'n Proto (zero-copy boundaries)\n\nFoundation uses seven performance planes. Each plane has its cost measured and enforced:\n\n```\n1. Direct dispatch        10–30 ns/op     (same-process, zero-alloc)\n2. Binary frames          20–80 ns/op     (borrowed views)\n3. Generated protobuf     ~370 ns/op      (typed cross-process)\n4. gRPC                   20–30 µs/op     (network machinery)\n5. JSON                   ~30 µs/op       (compatibility)\n6. Native FFI/SHM         (varies)        (trusted compute)\n7. Browser + WASM + SAB   (platform)      (where supported)\n```\n\n**Key rule**: The fastest lane must not pay the cost of the compatibility lane. This is measured automatically; regressions are caught before they land.\n\nRead more: `docs/foundation_benchmarks.md`\n\nEvery project generated from Foundation receives:\n\n**Multi-Tenant Isolation**— organization scope derived from authenticated context, never from client data** Event-Driven Nervous System**— canonical`requested → success / failed`\n\nlifecycle with correlation metadata**Hermes Hotplane**— node-local, memory-bounded, indexed read models that project database mutations in real-time** Resumable File Transfers**— progress-bearing, chunk-based upload/download with resumability** Bounded Worker Processing**— background jobs with exponential backoff, retry policies, and bounded queues** Unified Observability**— OpenTelemetry tracing, structured logs, circuit breakers, error taxonomy\n\nStart here → [ docs/foundation_quick_start.md](/nmxmxh/foundation/blob/main/docs/foundation_quick_start.md) (15 min) →\n\n[(walk-through) →](/nmxmxh/foundation/blob/main/docs/foundation_tour.md)\n\n`docs/foundation_tour.md`\n\n[(platform/project split)](/nmxmxh/foundation/blob/main/docs/foundation_architecture_contract.md)\n\n`docs/foundation_architecture_contract.md`\n\nStart here → [ docs/PHILOSOPHY.md](/nmxmxh/foundation/blob/main/docs/PHILOSOPHY.md) (why Foundation exists) →\n\n[→](/nmxmxh/foundation/blob/main/docs/foundation_architecture_contract.md)\n\n`docs/foundation_architecture_contract.md`\n\n[→](/nmxmxh/foundation/blob/main/docs/foundation_nervous_system.md)\n\n`docs/foundation_nervous_system.md`\n\n`docs/practice_controls.md`\n\nStart here → [ AGENTS.md](/nmxmxh/foundation/blob/main/AGENTS.md) →\n\n[→](/nmxmxh/foundation/blob/main/docs/foundation_glossary.md)\n\n`docs/foundation_glossary.md`\n\n[→](/nmxmxh/foundation/blob/main/docs/agent_operating_contract.md)\n\n`docs/agent_operating_contract.md`\n\n`docs/ai_threat_model.md`\n\n| Path | Purpose |\n|---|---|\n`server-kit/` |\nGo backend: registry, metadata, events, workers, resilience, observability, Hermes, eventlog, Redis, database, transfer, projection gateway, object storage, bulk operations, intelligence signals |\n`runtime-transport/` |\nProtocol contracts, command bus, route registry, binary codecs, Hermes projection schemas |\n`runtime-sdk/` |\nWASM/Rust/Go kernel, 4KB control-buffer, shared arena, runtime lane helpers |\n`runtime-native/` |\nTauri shell, secure storage, native frames, device dispatch |\n`frontend-kit/` |\nIndexedDB storage, metadata, runtime artifacts, transfer progress |\n`ui-minimal/` |\nShared UI primitives, theme tokens, motion helpers |\n`config-contracts/` |\nGenerated configuration schemas |\n`templates/` |\nScaffold templates copied into generated projects |\n`docs/` |\nArchitecture, practices, guides, security, performance, testing |\n`tooling/` |\nEnforcement scripts, manifests, lint configs |\n\n```\nmake generate-contracts      # Code gen (Protos → Go/TS)\nmake lint                    # All linters\nmake test                    # All tests\nmake check-rust              # Rust fmt, clippy, tests\nmake verify                  # Full CI suite\nmake check-practice-controls # Practice matrix\nmake check-doc-references    # Link validation\n\nmake docker-up               # Start local infra\nmake test-service-backed     # Tests with live DB/Redis\n```\n\nFrom the parent directory of `foundation`\n\n:\n\n```\n# New project\nnode foundation/cmd/ovasabi/bin/ovasabi.js init --profile=performance --name=my-app --foundation-dir foundation --skip-license\n\n# Or via shell script (legacy)\n./foundation/scripts/init-project.sh my-app full\n\n# Update existing project\nnode foundation/cmd/ovasabi/bin/ovasabi.js update --project-dir=/path/to/project --foundation-dir foundation --skip-license\n```\n\nGenerated projects consume Foundation through package boundaries. Do not import raw `foundation/*/ts/src`\n\nor `foundation/*/go`\n\ndirectly.\n\nFoundation bridges the **software deficit**: the gap between hardware performance (nanoseconds) and typical software stacks (milliseconds). It provides proven patterns for:\n\n**Responding instantly**— sub-microsecond operational reads via Hermes** Scaling safely**— bounded work, tenant isolation, circuit breakers** Observing clearly**— correlation IDs flowing through all layers** Evolving confidently**— enforced practices, contract verification, performance measurement\n\nFoundation is not for everyone. It's demanding. It requires discipline: thinking about performance trade-offs, writing adequate tests, understanding failure modes, reviewing gate verdicts. It's for teams that expect to build something ambitious.\n\nRead [ docs/PHILOSOPHY.md](/nmxmxh/foundation/blob/main/docs/PHILOSOPHY.md) for the full story.\n\n**Start here**: [ docs/README.md](/nmxmxh/foundation/blob/main/docs/README.md) is the documentation map.\n\n**Key reads** (in order):\n\n— concept lookup`docs/foundation_glossary.md`\n\n— 15-minute path`docs/foundation_quick_start.md`\n\n— walk-through one action`docs/foundation_tour.md`\n\n— ownership split`docs/foundation_architecture_contract.md`\n\n— lifecycle contract`docs/foundation_nervous_system.md`\n\n**If you're using AI tools**: [ AGENTS.md](/nmxmxh/foundation/blob/main/AGENTS.md) — agent workflows and evidence requirements\n\n**To understand why**: [ docs/PHILOSOPHY.md](/nmxmxh/foundation/blob/main/docs/PHILOSOPHY.md) — the motivation and design principles\n\nFoundation is actively evolving. The entire repository represents a work-in-progress baseline for production applications. Expect:\n\n- Continued refinement of contracts and practices\n- New performance planes (GPU compute, distributed tracing refinement)\n- Agentic coding patterns still being proven\n- Documentation expanding as usage patterns emerge\n\nContributions via research, agents, and human reviewers are how Foundation improves. Read [ docs/agent_operating_contract.md](/nmxmxh/foundation/blob/main/docs/agent_operating_contract.md) for evidence and handoff expectations.\n\nSee [ LICENSE](/nmxmxh/foundation/blob/main/LICENSE).", "url": "https://wpnews.pro/news/show-hn-foundation-a-different-approach-to-software-and-ai", "canonical_source": "https://github.com/nmxmxh/foundation", "published_at": "2026-07-04 12:46:17+00:00", "updated_at": "2026-07-04 13:20:55.461557+00:00", "lang": "en", "topics": ["developer-tools", "ai-infrastructure"], "entities": ["Ovasabi Foundation", "PostgreSQL", "Redis", "Protocol Buffers", "Cap'n Proto", "OpenTelemetry", "Go", "TypeScript"], "alternates": {"html": "https://wpnews.pro/news/show-hn-foundation-a-different-approach-to-software-and-ai", "markdown": "https://wpnews.pro/news/show-hn-foundation-a-different-approach-to-software-and-ai.md", "text": "https://wpnews.pro/news/show-hn-foundation-a-different-approach-to-software-and-ai.txt", "jsonld": "https://wpnews.pro/news/show-hn-foundation-a-different-approach-to-software-and-ai.jsonld"}}