The product answer
Silan Viking treats a research update as a sequence of decisions that can be inspected, resumed, and reversed.
- A quick capture becomes a dated record with stable identity.
- Moments, articles, projects, and résumé entries remain separate and gain
typed relationships. - CLI, source files, and the desktop workbench pass through the same Rust
validation and rebuild the same SQLite projection. - Editing, accepting an Agent proposal, publishing an item, and deploying a
site remain different actions. - The default MCP flow ends at a reviewable proposal.
- Runtime interactions and deployed-version facts remain server-owned and
cannot overwrite the authored source. silan guide, linting, and status commands explain the next missing step
instead of requiring the user to memorize the system.
The deeper architectural idea is a Personal Context System, but the product earns that architecture only through a concrete result: the next honest research update becomes easier to explain, publish, and maintain.
0 likes
Share:
No comments yet