PostgreSQL backup tool with Point-In-Time-Recovery and restore verification
TypeScript backupbackupsdatabasedatabase-backupdevopsdockergolangkubernetesmariadbmongodbmysqlpgpostgrespostgresqls3self-hostedsystem-administrationtoolsweb-ui
schema: spec-driven
context: |
Databasus - PostgreSQL/MySQL/MariaDB/MongoDB backup and restore platform,
self-hosted, Docker-deployed.
Stack: Go + Gin + GORM + PostgreSQL (backend/), Go CLI (agent/verification/),
React 19 + TypeScript + Vite + Ant Design 5 + Tailwind (frontend/),
Next.js 16 static export (website/).
Per-folder rules live in backend/AGENTS.md, agent/verification/AGENTS.md,
frontend/AGENTS.md, website/AGENTS.md; the root AGENTS.md holds the
engineering philosophy. A change under a folder answers to both.
Conventions that shape planning:
- Before any OpenSpec message or action, load the repository Humanizer skill
and apply its embedded mode to all agent-authored prose. Preserve exact
commands, paths, identifiers, schemas, templates, quotations and facts.
- English only in code, comments, identifiers, API strings and commit
messages. AGENTS.md enumerates every place translated end-user content
is allowed; a change that needs another one amends that rule explicitly
and with the user's approval, rather than assuming it.
- No unrequested backward compatibility. A change that breaks callers,
schemas, configs or APIs states the break; approved breaks delete the
old code rather than leaving a shim.
- No issue numbers in production code. The exception is a test pinning a
specific issue's behavior.
- Names state intent. Getters take Get, predicates read as questions,
booleans take is/can/has/should.
- Work happens on a Fedora host with the tools pinned in mise.toml.
Commands are just (repository root, backend, agent) and pnpm (frontend).
- Review hooks gate plans, finished turns, full proposals and full
implementations. Resolve their findings as the "Review hooks" section
of AGENTS.md says.
- Refactor the code the change touches while implementing, as the
"Refactoring within a feature" section of AGENTS.md says.
rules:
proposal:
- Humanize all prose in embedded mode before writing the artifact.
- Name the module AGENTS.md files the change answers to.
- Include an explicit out-of-scope list; scope creep is the main failure mode here.
- Mark anything that breaks existing callers, schemas, configs or APIs as BREAKING, and say what gets deleted rather than kept as a shim.
specs:
- Humanize all prose in embedded mode before writing the artifact.
- State behavior a user or a downstream system can observe. No Go types, React components, file paths or library names.
- Security-relevant behavior gets its own requirement, not a footnote.
design:
- Humanize all prose in embedded mode before writing the artifact.
- For each decision, name the alternatives rejected and why. A decision with no alternatives listed is a description, not a decision.
- Ground claims about current state in file:line references.
- Ground architecture decisions in the module AGENTS.md architecture rules and the accepted ADRs in adr/.
- Say which module AGENTS.md rules the approach is constrained by.
tasks:
- Humanize all prose in embedded mode before writing the artifact.
- Each task's verification is a local command the agent runs itself, never "should work". Valid checks are the tests of the touched packages and of the packages that test the same feature (just test-package ./internal/features/<feature>/... in backend/), just lint at the root or in a module, just build and just test in agent/verification, pnpm lint, pnpm typecheck, pnpm test, pnpm build, or an automated test that pins the behavior.
- Every task is one the agent can complete and verify on its own. Every task closes without the user stepping in and without the full backend suite. Keep these out of tasks and out of other tasks' verification, including a final verification task - the full backend suite (just test at the root), the Docker filesystem suite (just test-filesystem), deploys, CI pipeline runs, any check that needs a push, and manual app runs or browser clicking. The full backend suite resets the test containers other agents share, so it is left to the developer and CI.
- Order by dependency, smallest slice first when the work is repetitive.
- When the tasks add or change tests in a backend package, a verification agent package or the frontend, end tasks.md with a "## Change verification" section that runs every such package the tasks' verifications name. It is the last section, has no checkboxes and holds one code block fenced as sh, with one command per line. The full implementation review runs these commands, and only three forms are allowed - just test-package followed by package paths starting with ./ (runs in backend/), just --justfile agent/verification/Justfile test with nothing after it, and pnpm --dir frontend test with optional test paths or filters. Arguments hold only letters, digits, dots, slashes, underscores, hyphens, equals signs, at signs and colons. The hook tests in .agent-hooks/ need no section, because the hook's module check runs them.
- End the task list at the pre-commit boundary. The change is complete when implementation, required documentation, verification and mandatory review are finished, and the working tree is ready to commit.
- Never add tasks for committing, pushing, creating or updating a pull request, requesting pull request review, merging, or any later Git or repository-hosting workflow. Completion status updates must be ready for inclusion in the same commit as the implementation.
operations:
apply:
guidance:
- Run the linter for every directory the diff touches before finishing.
- Resolve every blocking review hook finding before finishing; never apply a scope finding without the user's consent.
- Never commit or push without explicit approval. A "pack" request, as the OpenSpec section of AGENTS.md describes it, is approval to commit, not to push. No AI attribution trailers in commit messages.
archive:
guidance:
- Confirm the module AGENTS.md files were updated if the change introduced a convention.