Commit graph

3 commits

Author SHA1 Message Date
Claude
496513e8ab
docs: Phase 4 implementation plan — 12 tasks across 4 phases
TDD plan for CoreDeno + Web Components: manifest types, ed25519
signing, object store, WC codegen, sidecar lifecycle, gRPC proto,
permission engine, marketplace index, and framework service wiring.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-17 18:55:25 +00:00
Claude
37b50abf57
docs: complete Phase 4 design — fill open sections from dAppServer archaeology
Polyfills: none needed (WebView2 is Chromium).
Object store: Go-managed SQLite via gRPC, 6 operations extracted.
Templated config generators: Go text/template in CoreGO.
Git-based plugin marketplace: Git repo as registry, clone-based distribution,
ed25519 verification, 7 marketplace RPC operations.
Complete RPC surface: 40+ procedures across auth, crypto, fs, process,
store, IPC, and marketplace namespaces.
Heritage table expanded to 4 tiers from 20-repo archaeological survey.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-17 18:39:14 +00:00
Claude
f5bf7cba81
docs: Phase 4 design — CoreDeno + Web Components
Approved architecture for the JavaScript runtime layer:
- CoreDeno (Deno sidecar) as module loader, I/O fortress, and dev toolchain
- go-html as Web Component factory (manifest → custom elements)
- .core/view.yml convention for declarative app definitions
- Signed application loading with ed25519 verification
- gRPC/Unix socket bridge between Deno and Go
- Gradual Angular migration to vanilla Web Components
- HLCRF slot composition with Shadow DOM isolation

Open sections (polyfills, object store, config generators, marketplace)
pending dAppServer heritage code review.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
2026-02-17 17:40:16 +00:00