Repository navigation
Decisions
github-actions[bot] edited this page Oct 19, 2026
·
53 revisions
Every question the project has answered, newest first.
| Question | Decision | Date | |
|---|---|---|---|
| Q-02 | How is the open-source library distributed and versioned? | GitHub releases only, with semantic version tags, and never npm (lib_github_release). | 16 Oct 2026 |
| Q-03 | Is provenance stored as graph history or as separate metadata? | A separate append-only log beside the notes, which the engine loads as graph data, so history can be queried. | 16 Oct 2026 |
| Q-04 | Do the display surfaces query the engines live, or work from exported snapshots? | Live on the owner's own devices, while web and corporate views get exported snapshots filtered by the boundary rules. | 16 Oct 2026 |
| Q-05 | Which graph backend: SQLite, an embedded graph database, a graph server, or an organisation's SQL database? | SQLite, with an embedded graph database possible later as a rebuild from the text. | 16 Oct 2026 |
| Q-06 | How do the authored notes and the graph store stay in step: export and import, or live sync? | Live and one way: the engine watches the notes and updates the store, and every edit is written to the text first. | 16 Oct 2026 |
| Q-07 | Should contested links change query results directly, or only guide the eye? | Guide the eye: results stay the same, contested things are marked, and filtering them out is the user's choice. | 16 Oct 2026 |
| Q-13 | Some original design decisions were not recovered and others survive only as paraphrase: do the requirements resting on them stand? | Review each of the four requirements before slice 7 starts, and until then they stand as written. | 16 Oct 2026 |
Made from requirements/editor-requirements.gql at d0d6f56 on 19 Oct 2026. This page is generated: change the repository, not this page, as edits here are overwritten.