ODS V3 Pre-Release: Public testing and refinement ahead of the official V3 launch. Turn your PC, Mac, or Linux box into a private AI server.
Python ai-agentsamdcomfyuidockerllama-cppllmlocal-ain8nnvidiaopen-webuiragself-hostedspeech-to-textstrix-halotext-to-speechworkflow-automation
title: Pixel documentation doc_type: reference audience: [owner, operator, contributor, security-reviewer, maintainer] feature_status: mixed owners: [documentation] sources_of_truth: [README.md, pixel, RELEASE-MANIFEST.json, QUALIFICATION-MATRIX.json, OPENCLAW-COMPATIBILITY.json] last_verified_at: 2026-08-27
Pixel documentation
Start with the job you need to do. Status words in these pages are evidence boundaries, not marketing labels: source presence, an authored test, or a generated receipt does not by itself prove support, deployment, or live acceptance.
Start here
| Your job | Start with | Then use |
|---|---|---|
| Understand what this checkout claims | Current status | Repository README and qualification contract |
| Install or evaluate Pixel | Requirements and clean-host quickstart | First deployment and post-install checklist |
| Configure or customize Pixel | Configuration source map | Configuration overview, extension chooser, and client onboarding |
| Find a command | CLI reference | The command's guide, preview, or help output |
| Understand a data contract | Schema catalog | The linked schema and its owning component |
| Use Pixel for the first time | First real conversation | Status and evidence |
| Operate or recover Pixel | Operations runbook | Upgrade and rollback, incident response, and support packet |
| Review security and privacy | Security overview | Threat model and security assurance |
| Change code or docs | Contributing | Documentation contract and architecture |
| Review release or qualification evidence | Qualification | Compatibility record and the exact versioned live audit linked from status |
Current foundation
The index, status, CLI, schema, and configuration pages are additive. Existing root guides remain in place while their contracts and inbound links are audited. Versioned live audits, compatibility files, qualification records, and release artifacts have not been moved.
Owner journey
- Check the host and private-input requirements.
- Follow the clean-host quickstart.
- Use the first-deployment decision tree for only the enabled limbs.
- Complete client onboarding and handoff when another owner/client will operate the deployment.
- Complete the post-install checklist.
- Run a first real configured-model conversation.
- Use status and evidence to keep repository, installed-host, synthetic, live-backend, recovery, and acceptance claims separate.
Concepts
- What is Pixel?
- Architecture overview
- Trust, authority, and evidence
- Lifecycle and state
- Capability status model
- Glossary
Configuration
- Configuration overview
- Deployment profiles
- Capability profiles
- Models and providers
- Source limbs
- Operations and Frontier
- Client overlays
- Generated configuration source map
Generated reference
- CLI reference and command-family matrix
- Schema catalog
- Configuration source map
- Services, paths, and ports
- Support and qualification matrix
- Release evidence index
- Complete Markdown inventory
Use Pixel
- First real conversation
- Control surface
- Sources and proposals
- Operations
- Frontier review
- Deep Work status and source boundary
Extend Pixel
- Choose an extension point
- Signed projection limbs
- Local capability declarations
- Operations action packs
- Frontier task restriction packs
- Gateway extensions
- Validated extension workflow example
Security and privacy
- Security overview
- Threat model guide
- Boundary reference
- Security assurance
- Evaluation and qualification boundaries
- Sealed-corpus custody
Operations
- Runbook
- Command cheat sheet
- Verify and diagnose
- Backup and restore
- Update and rollback
- Gateway token rotation
- Incident response entry point
- Monitoring and logs
- Troubleshooting
- Safe support packet
- Owner and operator FAQ
- Decommission
Releases and qualification
- Release overview
- Maintainer runbook
- Release qualification
- OpenClaw upstream intake
- Release failure guide
- Generated release evidence index
Contributing and maintenance
- Codebase map
- Development setup
- Testing
- High-risk change map
- Generated and private files
- Pull request guide
- Documentation contract
Documentation rules
- Generated pages say how to regenerate them and are checked for drift.
- Maintained pages identify their audience, document type, feature status, owners, and source-of-truth paths.
- Current product guides do not copy release versions or provider pins from generated contracts into prose.
- Historical evidence stays historical. Candidate evidence is not rewritten as Supported or live acceptance.
- Private paths, credentials, user content, and live evidence do not belong in examples.
See the documentation contract for the enforced metadata and contribution rules.