qv-registry-autobase-patterns
Skill697 starsChanged 18 days agoApache-2.0View on GitHub
Reference material for Autobase, HyperDB, and multi-writer patterns in the QVAC registry server. Use when working with Autobase, HyperDB schemas, blind pairing/peering, Hyperdispatch, or debugging Corestore/replication issues.
Files
Registry Autobase Patterns
What
Reference material for Autobase, HyperDB, Hyperdispatch, and multi-writer distributed database patterns used in the QVAC registry server. Covers schema design, blind pairing/peering, multi-writer deployment, RPC layer setup, and HyperDB query patterns.
When to Use
- Working with Autobase configuration, apply functions, or multi-writer patterns
- Working with HyperDB schemas, collections, indexes, or query patterns
- Implementing or debugging blind pairing (invites) or blind peering (mirrors)
- Setting up Hyperdispatch routers or operation encoding
- Deploying or managing multi-writer instances (3-writer setup, writer rotation)
- Working with Hyperswarm networking, Protomux RPC, or peer discovery
- Debugging Corestore, Hypercore, or replication issues
References
| File | Content |
references/autobase-patterns.md | Autobase + HyperDB multi-writer architecture: blind pairing, blind peering, schema build pipeline, router setup, common operations |
references/implementation-kb.md | Registry-specific gotchas: Corestore locking, named keypairs, writer vs indexer, Protomux connection order |
references/hyperdb-learnings.md | HyperDB workshop: schema definition, CRUD operations, indexes, query patterns, networking, testing |
references/hyperdb-autobase-learnings.md | Multi-writer workshop: Autobase architecture, Hyperdispatch, RPC layer, 3-writer deployment, disaster recovery |
In this repository56 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .github/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/agent-integrations.mdcCursor rule
- .cursor/rules/cpp/string-api-conventions.mdcCursor rule
- .cursor/rules/devops/main.mdcCursor rule
- .cursor/rules/no-remote-code-execution.mdcCursor rule
- .cursor/rules/qip-triage.mdcCursor rule
- .cursor/rules/sdk/commit-and-pr-format.mdcCursor rule
- .cursor/rules/sdk/error-handling.mdcCursor rule
- .cursor/rules/sdk/first-class-product-parity.mdcCursor rule
- .cursor/rules/sdk/main.mdcCursor rule
- .cursor/rules/sdk/public-constants-contract.mdcCursor rule
- .cursor/rules/sdk/request-lifecycle-primitives.mdcCursor rule
- .cursor/rules/sdk/sdk-pod-packages.mdcCursor rule
- .cursor/rules/sdk/skill-authoring-guidelines.mdcCursor rule
- cpp-string-api-reviewSkill
- qv-addon-changelogSkill
- qv-addon-pr-createSkill
- qv-addon-release-notesSkill
- qv-agent-stack-syncSkill
- qv-asana-syncSkill
- qv-daily-work-updateSkill
- qv-dev-diary-setupSkill
- qv-dev-diarySkill
- qv-devops-daily-updateSkill
- qv-devops-pr-createSkill
- qv-devops-pr-reviewSkill
- qv-devops-pr-statusSkill
- qv-devops-runner-queueSkill
- qv-devops-why-my-pr-notSkill
- qv-docs-solution-createSkill
- qv-docs-updateSkill
- qv-holepunch-devSkill
- qv-merge-guard-wireSkill
- qv-mobile-test-dispatchSkill
- qv-notice-generateSkill
- qv-pr-mineSkill
- qv-pr-reviewSkill
- qv-pr-testSkill
- qv-qip-createSkill
- qv-qip-reviewSkill
- qv-qip-triageSkill
- qv-quality-reportingSkill
- qv-release-trainSkill
- qv-sdk-backmergeSkill
- qv-sdk-changelogSkill
- qv-sdk-e2e-createSkill
- qv-sdk-inference-versionSkill
- qv-sdk-pr-createSkill
- qv-sdk-pr-statusSkill
- qv-sdk-update-modelsSkill
- qv-skill-listSkill
- setupSkill
- setupSkill
- qv-nx-ciSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

