This repository hosts a living proposal for building a cloud-agnostic metadata platform on top of SQLite. The goal is to capture design decisions, research notes, and implementation plans in a highly collaborative format that works for both humans and automation agents.
- Proposal
- Working Agreement
- Research Notes
- Issues
- Project Board: Created automatically once the classic project API becomes available
git clone https://github.com/ganesh47/sqlite-metadata-proposal.git
cd sqlite-metadata-proposal
gh repo sync- Review open issues and the project board to understand current priorities.
- Open or select an issue (Planning / Research template) and self-assign.
- Create a feature branch (
git switch -c docs/section-update-<issue#>). - Make changes, update the proposal or notes, and open a pull request using the template.
- Ensure CI checks (markdown lint, link check) pass before requesting review.
markdown-lint: Runs on PRs and pushes touching.mdto enforce style consistency.link-check: Runs on PRs and a weekly schedule to keep references fresh.auto-assign: Runs on PRs and issues to auto-assign work to @ganesh47.spec-task-sync: Runs weekly (and via manual trigger) to mirrorspecs/tasks.jsonentries into GitHub issues with correct labels/assignees.
The project board uses the Stage single-select field with steps Backlog →
Selected → In Progress → Review → Done.
- Branch per task; keep history tidy with squash merges.
- Reference issues in commits/PRs (
Closes #<id>). - Capture context in
docs/notes/YYYY-MM-DD.mdfor research spikes. - Use labels + milestones to track progress toward proposal maturity.
- M1 – Foundations: Complete scaffolding, workflows, and baseline proposal structure.
- M2 – Architecture Draft: Produce the first end-to-end design narrative.
- M3 – Implementation Plan: Translate the proposal into actionable project work.
Open a discussion if you have questions or suggestions: Discussions will be enabled soon to support broader async collaboration.