K-Web specs

-[] TODO Merge all of this into a mega doc / page, human readable with a friendly summary of everything on the first page / pages. A script can later split it up automatically to be used by coding agents.

This folder is the source of truth for how K-Web behaves and how it is built. These docs are written to be operational: they define module boundaries, event contracts, data model, and “done means”.

Start here

• Vision: ./vision.md
• Principles: ./principles.md
• Architecture: ./architecture.md
• Data model: ./data-model.md
• Event contracts: ./event-contracts.md
• Authoring: ./authoring.md

Module specs

• App shell: ./modules/app-shell.md
• Graph: ./modules/graph.md
• Timeline: ./modules/timeline.md
• Map / globe: ./modules/map.md
• Bio / reader: ./modules/bio.md
• Search: ./modules/search.md
• Trails: ./modules/trails.md
• Editor (nodes + links): ./modules/editor.md
• Web picker: ./modules/web-picker.md
• Spheres (optional): ./modules/spheres.md
• Inspector (dev harness): ./modules/inspector.md

How we build

• Workflow: ./workflow.md
• Testing (smoke tour): ./testing.md
• Roadmap: ./roadmap.md
• ADRs: ./adr/README.md
• Glossary: ./glossary.md

Assets

Put screenshots and diagrams in ./assets/ and reference them with relative links.

• Assets folder: ./assets/README.md

Notes

• Custom webs are supported from day one.
• Data source is secondary. Wikipedia/Wikidata enrichment is optional and a future subproject.
• Editing and creating webs/nodes/links is built in from the start, intended to replace the old workflow (building in The Brain).