Kelryvo is a self-hosted, Oracle-first Database DevOps platform. The runnable product combines a TypeScript/Fastify API, React browser app and PostgreSQL metadata.
Start with product requirements, current capabilities and roadmap. It is the authoritative product document, including the instance master credential architecture. The next-session entry links the implementation and safety guides.
Connect one Oracle instance credential reference, discover schemas and assign several of them to a project. Author or import SQL, validate scope, prepare a retained plan, obtain independent approval, execute through the trusted worker and inspect immutable history and audit. Credential changes stale old authority without rewriting evidence.
Automatic SQL is restricted to a conservative schema DDL subset; approval cannot override scope denial. Live Oracle evidence is limited to the explicitly attested disposable Oracle Free PDB lab and tested statements. Production installation, other versions/topologies and the full fault/recovery matrix require separate acceptance. The API alone cannot install execution authority. See the product requirements and Oracle acceptance guide for exact boundaries.
Use Node 22.23.3, npm 10.9.9 and Python 3.11+:
npm ci --ignore-scripts --no-audit --no-fund
npm run check
npm run status
npm run nextOffline checks need no database credentials; optional database/parser cases may skip. Testing guidance explains full PostgreSQL/API, Chromium and source-installation acceptance. Tracker status preserves original catalog acceptance and must not be read as a delivered-feature percentage.
Requires Git, Docker and Linux x64 for the pinned parser preparation:
npm run local:prepare
npm run devOpen http://127.0.0.1:4317. Preparation obtains pinned parser tools and the PostgreSQL image. Startup uses isolated local metadata on port 55432, a persistent Docker volume, a demo Git repository and private local tokens in .cache/local-product/config.json (0600). Explicitly activate membership and grant actors before project writes. Use separate developer and approver identities; HTTP mode keeps the bearer in browser memory. Target credentials remain references.
For secure browser sessions, supply a trusted loopback certificate/private key with the private permissions documented in the local product guide:
npm run dev -- --tls-cert /absolute/private/tls/server-chain.pem --tls-key /absolute/private/tls/server-key.pemOpen https://127.0.0.1:4317. HTTPS uses revocable Secure/HttpOnly cookies, CSRF protection and expiry. The guide covers operator provisioning, API contracts, workflow, shutdown and current boundaries. No startup command authorizes Oracle access.
| Path | Purpose |
|---|---|
| Product requirements | Current state, stable requirement IDs, remaining backlog, priority and acceptance criteria |
| Architecture contracts | Ownership, target identity, migration safety and compatibility decisions |
| UI conventions | Shared interactions and accessibility requirements |
docs/development/ |
Concrete API, test, runtime, release and Oracle acceptance guides |
| Retained tracker | Original catalog/task contracts, immutable evidence references and Oracle case gates |
apps/api, apps/web, apps/worker, packages/ |
Product implementation |
scripts/, tests/, .github/workflows/ |
Tooling and local/hosted acceptance |
docs/decisions/, docs/dependencies/ |
Decision history, pinned dependencies, licenses and notices |
docs/inputs/, experiments/db-devops-wp0/, evidence/ |
Immutable historical inputs, isolated feasibility harness and append-only observations |
Historical MVP, Phase 1 and design handoff documents are dated references, not active work queues. Git history preserves removed obsolete planning. Keep original evidence and safety contracts intact.
CONTRIBUTING.md covers contribution and CI rules. Controlled execution, runtime operations and the disposable Oracle suite describe separate live gates. Never automatically replay ambiguous DDL.
Independently authored code uses PolyForm Shield 1.0.0; third-party grants/notices remain separate. See license scope and provisional naming and dependency evidence. Internal behavioral research is not publication material.
Build a reproducible local source bundle with npm run release:local -- --output /absolute/existing-parent/new-release-directory; follow the local release guide. Publishing or deploying requires explicit task authorization.