Skip to content

docs: keep design proposals and decision records under standard names - #412

Merged
vishr merged 3 commits into
mainfrom
docs/proposals
Oct 30, 2026
Merged

vishr merged 3 commits into
mainfrom
docs/proposals

Conversation

@vishr

@vishr vishr commented Oct 30, 2026

Copy link
Copy Markdown
Member

What changed

Closes #406.

  • Design docs move from docs/specs/ to numbered proposals in
    docs/proposals/0001–0004, with history kept and a status header added.
  • docs/adr/ records seven settled decisions with an index and a template:
    environment-only configuration; SQLite with Goose and sqlc; the pinned
    DuckDB engine and batch format 4; no legacy paths; CalVer; one structured
    query path; a hand-written FanQL parser.
  • CONTRIBUTING and AGENTS.md point to both and keep agent plans out of the
    repository.

Verification

  • just check (pre-push); links checked
  • No credentials, private telemetry, host details, or enterprise-only source

vishr added 3 commits October 30, 2026 12:24
Design docs move from dated files in docs/specs to numbered proposals
in docs/proposals with a status header, and settled decisions get short
records in docs/adr. CONTRIBUTING and AGENTS.md point to both and keep
agent working plans out of the repository.

Closes #406.
The no-legacy record now lists the rules AGENTS.md sets, the structured
query record describes FanQL filters accurately and lists the builder as
planned, and claims the code does not support are removed.

Refs #406.
@vishr
vishr merged commit 520fc63 into main Oct 30, 2026
17 checks passed
@vishr
vishr deleted the docs/proposals branch October 30, 2026 22:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

docs: keep design proposals and decision records under standard names

1 participant