| type | Knowledge Pack |
|---|---|
| title | Lethean knowledge packs |
| description | Curated reference material for the Lethean (dAppCore) frameworks — self-contained knowledge bases for agents and developers |
Curated reference material for the Lethean (dAppCore) frameworks. Each pack is a self-contained knowledge base an agent or a developer can read to understand a framework, find the right package, and work with it correctly.
These packs are written for agents: factual, navigable, and kept close to the
source. They complement the canonical specifications in plans/ rather than
replacing them.
| Framework | Description | Repository |
|---|---|---|
| CoreGo | Zero-dependency Go framework | github.com/dappcore/go |
| CoreGUI | Wails v3 GUI framework | github.com/dappcore/gui |
| CoreTS | TypeScript frontend framework (Deno) | github.com/dappcore/ts |
| CoreCLI | CLI framework | github.com/dappcore/cli |
| CorePlay | Game platform (engines, bundles) | github.com/dappcore/play |
| CorePHP | PHP framework (25 repos) | github.com/dappcore/php |
Each pack follows a consistent layout:
knowledge-packs/<framework>/
├── README.md Framework overview and usage
├── INDEX.md Package or component catalogue
├── CATALOG.md Auto-extracted schemas, structs, actions (generated — do not hand-edit)
└── <area>/ One folder per feature area, each with a README.md
Multi-repo frameworks (CoreGo, CorePHP) nest per-repo packs under pkg/:
corego/pkg/<package>/ and corephp/pkg/<repo>/, each with README, INDEX,
and — for Go repos — a generated CATALOG.
A README covers the framework's purpose, architecture, core components, a
getting-started path, when to use it (and when not to), and links to related
packs. CATALOG files are regenerated with plans/tools/lethean-plan/scripts/schema.py
after code changes.
Knowledge packs sit between the canonical specifications and the OKF bundle.
| Location | Purpose | Audience |
|---|---|---|
plans/ |
Canonical specifications — RFCs, design documents | Humans and agents |
knowledge-packs/ |
Curated, agent-oriented reference | Agents and humans |
Source-of-truth order: plans/ → knowledge-packs/.
| Framework | Language | Purpose | Notes |
|---|---|---|---|
| CoreGo | Go | Backend primitives | Zero-dependency, SPOR, Result pattern |
| CoreGUI | Go + TS | Desktop apps | Wails v3, provider mounting, window management |
| CoreTS | TypeScript | Frontend | Deno, native custom elements, gRPC bridge to Go |
| CoreCLI | Go | CLI tools | Command runtime, Frame TUI, prompts, i18n |
| CorePlay | Go | Game platform | Emulator engines (DOSBox and others), bundles, Shield |
| CorePHP | PHP | Web apps | Laravel modular monolith, 25 repos |
- Start with CoreGo. It is the foundation the other frameworks build on.
- Check a framework's purpose before reaching for it; use the one that fits the job.
- Follow the RFC links to the canonical spec when you need authoritative detail.
- Cross-reference related packs, linked at the foot of each README.
Each README is plain Markdown — read it directly, or load it as context. Packs are
addressed by framework name under knowledge-packs/<framework>/.
Updated when frameworks are added or change, or when patterns settle. Original drafts by Mistral Vibe.
plans/— canonical specifications