Convex

Build me a focused reactive backend workflow for the personal core of Convex. Requirements:

- Use exactly this stack: Go 1.24 + Docker + SQLite. Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Paid product context: Managed database, functions, realtime sync, file storage, and auth helpers. Build only this DIY scope: Build a single-server deployment panel for one user that accepts a repository, builds a container, deploys it, shows logs, and supports rollback.
- For reactive backend, accept a repository revision and a deployment target with declared environment variables.
- Build an immutable artifact and record build output, health-check result, and deployment ID.
- Show logs, current revision, and one-click rollback to a known healthy artifact.
- Use a focused reactive backend input, review, and export interface. Required input or access: Linux VPS; Docker.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest.
- Out of scope: 24-hour operations and support; managed global infrastructure. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

# AGENTS.md — Build guide for Convex

## Project scope
Build a single-server deployment panel for one user that accepts a repository, builds a container, deploys it, shows logs, and supports rollback.

Catalogue verdict: no. Do not mistake the interface for the product. Convex's durable value is infrastructure, uptime, operations, which a solo one-shot build cannot reproduce responsibly. The prompt therefore builds only the closest honest personal consolation tool.
Use the implementation prompt below to define the deliverable. Complete each phase's acceptance checks before extending the scope.

## Working agreement
- Inspect the repository and its existing instructions before choosing paths, dependencies or commands. Keep one coherent stack and explain changes to the proposed architecture.
- Plan a vertical slice that accepts a real input and produces the useful output described below. Persist only the state the prompt calls for; respect memory-only and upstream-managed workflows. Use fixtures only when they are clearly labelled.
- After scaffolding, document the actual install, development, check and build commands in README and keep them synchronized with the package or project manifest. Do not report commands as successful unless they ran.
- Work in small steps. At handoff, list implemented flows, checks actually performed, remaining blockers, and any credentials or provider setup the owner must supply.
- Do not publish, spend money, contact customers, delete source data or run irreversible migrations without the project owner's authorization.

## Prerequisites
- Linux VPS
- Docker
- DNS control
- Explicit README warning that this is a consolation build, not a production replacement

## Stack and architecture
- Use exactly this stack: Go 1.24 + Docker + SQLite.
- Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Interface for this reactive backend workflow: a focused reactive backend input, review, and export interface.

## Security and data integrity
- A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest.
- Validate imported records and file paths; keep user data within the storage location named in the prompt.
- State the practical limit: 24-hour operations and support.

## Agent implementation rules
- Project rule, data: Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Project rule, behavior: For reactive backend, accept a repository revision and a deployment target with declared environment variables.
- Project rule, recovery: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest.

## Optional agent skills and references
No installable skill is listed for this guide; use the project rules and the stack documentation.

Read the linked SKILL.md and its dependencies before adding a skill. Select only the skills matching this project's runtime and task; their documentation does not supply API access, credentials or approval to perform external actions. Pin the reviewed revision where the tool supports it. Follow the chosen agent's documented project-level installation mechanism.

## Distribution ideas
These are optional planning notes. Obtain the owner's approval before publishing or contacting anyone.
- Demonstrate this reactive backend operation with sample or user-owned data: For reactive backend, accept a repository revision and a deployment target with declared environment variables.
- Show a concrete result or export: Show logs, current revision, and one-click rollback to a known healthy artifact.
- State the practical limit: 24-hour operations and support.

## Engineering roadmap
1. Phase 1, architecture and data: Use exactly this stack: Go 1.24 + Docker + SQLite. Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
2. Phase 2, implement: For reactive backend, accept a repository revision and a deployment target with declared environment variables.
3. Phase 3, implement: Build an immutable artifact and record build output, health-check result, and deployment ID.
4. Phase 4, review and output: Show logs, current revision, and one-click rollback to a known healthy artifact.
5. Phase 5, recovery and acceptance: Verify this invariant with a saved fixture: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest. State the practical limit: 24-hour operations and support.

## Paid-product capabilities outside this build
- 24-hour operations and support
- managed global infrastructure
- multi-region failover
- DDoS protection and compliance

## Implementation prompt
Build me a focused reactive backend workflow for the personal core of Convex. Requirements:

- Use exactly this stack: Go 1.24 + Docker + SQLite. Model repositories, builds, deployments, logs, and rollback points; store source IDs and timestamps for each.
- Paid product context: Managed database, functions, realtime sync, file storage, and auth helpers. Build only this DIY scope: Build a single-server deployment panel for one user that accepts a repository, builds a container, deploys it, shows logs, and supports rollback.
- For reactive backend, accept a repository revision and a deployment target with declared environment variables.
- Build an immutable artifact and record build output, health-check result, and deployment ID.
- Show logs, current revision, and one-click rollback to a known healthy artifact.
- Use a focused reactive backend input, review, and export interface. Required input or access: Linux VPS; Docker.
- Acceptance: with one labelled sample, show the input, saved intermediate state, and exported result; verify this invariant: A failed health check must not replace the last healthy deployment; rollback must recover its exact artifact digest.
- Out of scope: 24-hour operations and support; managed global infrastructure. Keep this a personal, inspectable workflow.
- Include a README with setup, a sample input, required keys or permissions, data location, and the supported scope.

## Completion evidence
Demonstrate the prompt's acceptance scenarios against the scoped workflow. Include setup from a clean checkout and failure recovery. Check persistence across restart and export/restore only for the state the prompt says to store; for memory-only tools, confirm that temporary content is discarded as specified. Record actual results and remaining limitations. A detailed plan alone does not establish a working replacement.