Oprow Continuum

Inspiration

Coding agents can read plausible configuration values that are stale. Ordinary retrieval finds similar text; it does not establish which fact is current, what it replaced, or which immutable event proves the answer.

What it does

Oprow Continuum sits between a coding agent and a repository change. An agent submits a structured assumption or unified diff through MCP or OpenAPI. Oprow checks versioned repository receipts and returns BLOCK, ALLOW, or ABSTAIN. Findings include immutable receipt citations and a stable review ID. Review is read-only and never silently mutates the repository.

How we built it

CockroachDB is the durable memory layer for repository events, supersession edges, active capsules, and observation receipts. Transactional point reads recover First, Previous, and Current evidence without replaying full Git history. The CockroachDB Agent Skills Repo informed idempotent writes, collision rejection, and transaction retry behavior; ccloud CLI produced a read-only, hashed audit of cluster identity, database inventory, and networking.

The service runs on AWS from a CodeBuild-produced ECR image. EC2 hosts the container, CloudFront provides public HTTPS with dynamic caching disabled, Secrets Manager holds runtime credentials, S3 stores reproducible build artifacts, and Amazon Bedrock Nova explains only bounded evidence selected by the trusted verifier. Bedrock is not the source of temporal truth.

The Modus_X connection

Oprow grew from Modus_X bounded recurrent and associative memory research. It preserves the systems idea that durable history can grow while active verification memory remains bounded. A learned shared-stream controller failed repository-disjoint transfer and is deliberately excluded from the production decision path; the shipped verifier uses a bounded hot receipt cache with exact CockroachDB provenance.

What we learned

Immediate memory accuracy is not enough. Delayed queries, repository-disjoint evaluation, reset controls, stale-recall accounting, exact citations, and fail-closed behavior are necessary for credible agent memory.

What's next

Authenticated private repositories, webhook-based incremental ingestion, organization policies, and wider typed fact extractors, while retaining bounded evidence, immutable receipts, no silent mutation, and explicit abstention.

Built With

• amazon-bedrock
• amazon-ecr
• amazon-web-services
• aws-cloudfront
• aws-codebuild
• aws-ec2
• aws-secrets-manager
• ccloud-cli
• cockroachdb
• cockroachdb-agent-skills
• fastapi
• mcp
• python
• pytorch