Architecture
Codebase organization
The proposed platform monorepo, service boundaries, packages, and language allocation.
v1 design baseline. This page specifies intended behavior. Delivery and validation are tracked in the implementation plan; it is not a claim that the platform is already implemented.
This is the proposed platform repository layout. This intrnl-docs checkout is the documentation website, not that platform implementation.
A practical monorepo:
intrnl-platform/
├── apps/
│ └── control-plane/ Laravel + Filament
│
├── services/
│ ├── edge-gateway/ Go
│ ├── runtime-agent/ Go
│ ├── sandbox-runner/ Go
│ ├── db-binding/ Go or Rust
│ ├── kv-binding/ Go
│ ├── egress-proxy/ Go
│ └── telemetry-collector/ config/distribution
│
├── packages/
│ ├── contracts/ JSON Schema/OpenAPI
│ ├── policy-engine/ shared policy model
│ ├── sdk-js/ @intrnl/sdk
│ ├── nuxt-module/ @intrnl/nuxt
│ ├── local-runtime/ development adapters
│ └── test-fixtures/
│
├── templates/
│ └── nuxt-app/
│
├── infra/
│ ├── terraform/
│ ├── helm/
│ ├── kubernetes/
│ └── images/
│
├── docs/
│ ├── architecture/
│ ├── adr/
│ ├── runtime-contract/
│ ├── security/
│ └── runbooks/
│
└── tests/
├── e2e/
├── security/
├── compatibility/
└── disaster-recovery/
Language allocation
- PHP/Laravel: business workflows, authorization, Filament, REST, MCP orchestration.
- Go: gateways, agents, proxies, sandbox orchestration, high-concurrency infrastructure services.
- TypeScript: SDK, Nuxt module, templates, local developer tooling.
- SQL: explicit platform schema and app migrations.
- Terraform/Helm: infrastructure and runtime-cluster installation.