Small tools. Solid foundations.
A standalone documentation hub for OCode.js and selected Velclaw engineering projects. This repository organizes documentation, design references, source audits, and implementation plans; it does not merge application codebases or automatically write to other repositories.
- Project overview and architecture: docs/ECOSYSTEM.md
- OCode.js implementation roadmap: docs/ROADMAP.md
- Agent Skills Directory: docs/AGENT-SKILLS-DIRECTORY.md — curated skill categories, installation command, platform notes, and safety checklist.
- Plugin development for ChatGPT and Codex: docs/OPENAI-PLUGIN-DEVELOPMENT.md — plugin architecture, Skills, MCP, authentication, testing, publishing, metadata, UI, and security.
- x-bo by OCODE.js product/design blueprint: docs/X-BO-BY-OCODEJS-BLUEPRINT.md — target architecture, UX workflow, design system, GitHub/release gates, security, and staged implementation.
- Source inventory and audit findings: docs/SOURCE-AUDIT.md
- Content review: docs/CONTENT-REVIEW.md
- Canonical alignment plan: docs/CANONICAL-ALIGNMENT-PLAN.md
- Integration contracts and release gates: docs/INTEGRATION-MATRIX.md
- Verification plan: docs/VERIFICATION-PLAN.md
- Repository index: docs/REPOSITORY-INDEX.md
- Implementation findings: docs/IMPLEMENTATION-FINDINGS.md
- Operations and release gates: docs/OPERATIONS-AND-RELEASE-GATES.md
- Documentation quality gates: docs/DOCUMENTATION-AND-QUALITY-GATES.md
- Design system: DESIGN_SYSTEM.md
- Brand/rebrand reference: OCodejs-by-Velclaw-Full-Rebrand.pdf
This hub links to projects for reference and audit purposes only. They remain independent repositories:
- OCodejs/OCodejs
- Velclaw/OCodejs
- VelCli
- X-BO
- VelclawHost
- velclaw-deploy
- OAuth
- TechDocs
- VELCLAW
- Docs UI Reference
- Velclaw-OCodejs
Repository links are references, not evidence that every source file has been inspected or that a project is production-ready. Product claims must be supported by source code, tests, or an explicit architecture decision.
The documentation site now has a floating assistant launcher and a standalone chatbot.html page. The chatbot runtime remains a separate Next.js application in OCodejs/chatbot; it must be deployed independently on Vercel because GitHub Pages serves static files only.
- Public endpoint configuration: chatbot-config.js — set
window.OCODEJS_CHATBOT_URLto the HTTPS Vercel deployment URL after deployment. - Standalone page: chatbot.html.
- Integration notes and environment checklist: docs/CHATBOT-INTEGRATION.md.
Do not put API keys, database URLs, authentication secrets, or populated .env files in this repository. Configure AUTH_SECRET, POSTGRES_URL, REDIS_URL, and any required Blob/AI Gateway credentials in Vercel Project Settings or the relevant Vercel integrations. The Vercel project creation request for OCodejs/chatbot was blocked by a 403 permission error, so the live endpoint has not yet been verified and the public URL is intentionally unset.
The current priority is to improve this repository itself: navigation, link integrity, mobile usability, accessibility, content accuracy, and repeatable documentation checks. Cross-repository synchronization has been discontinued; this project will not push documentation snapshots into other repositories.
No production deployment, secret migration, or database modification is part of this documentation work.
Make changes on a branch and submit a pull request. Preserve source links, licensing, and attribution. Never commit credentials, populated environment files, or secrets.
- Machine-readable repository inventory: ecosystem/repositories.json
- Inventory validation script: scripts/validate-ecosystem.py
- Implementation roadmap: docs/ROADMAP.md
