feat: add module contracts and discovery
This commit is contained in:
@@ -56,11 +56,14 @@ surfaces.
|
||||
- Private objects use signed access and namespaced storage paths.
|
||||
- Every network service starts from least-privilege and local-only development defaults.
|
||||
|
||||
## Phase 1 status
|
||||
## Current implementation status
|
||||
|
||||
Implemented now: monorepo/tooling, strict TypeScript policy, repository-boundary validation,
|
||||
tests, base CI, PostgreSQL, and a development S3-compatible object store.
|
||||
Implemented now: the Phase 1 repository and infrastructure foundation plus public module contracts,
|
||||
the Module SDK manifest API, static versioned module manifests, automatic filesystem discovery,
|
||||
compatibility/dependency ordering, structured discovery failures, and a backend-only module
|
||||
template. Core can validate zero or more modules without importing their server behavior.
|
||||
|
||||
Target architecture, not yet implemented: Core runtime, module discovery and lifecycle, Drizzle
|
||||
schema aggregation/migrations, Better Auth, permissions, storage service, Module SDK, Surface
|
||||
SDK, capability/resource/action registries, API server, dashboard, Builder, and reference modules.
|
||||
Target architecture, not yet implemented: lifecycle execution and runtime registration, Drizzle
|
||||
schema aggregation/migrations, Better Auth, permissions, physical storage-bucket provisioning,
|
||||
Surface SDK, capability/resource/action registries, API server, dashboard, Builder, and reference
|
||||
feature modules.
|
||||
|
||||
Reference in New Issue
Block a user