7.4 Documentation baseline and updates
These docs were checked on 2026-09-23 against the current personal Web Alpha source. Repository package versions are 0.2.0-alpha.3, with subsequent unreleased changes also present. This does not mean those changes have been released as an official version.
What these docs cover
- Installation, model configuration, your first task, and your first team.
- Group collaboration, colleagues, tasks, automations, business areas, knowledge, capabilities, and the marketplace.
- Auto Dream summaries, automatic saving, sources, and withdrawal; digital twin sample boundaries.
- Local maintenance, permissions, development paths, skills, and a read-only MCP example.
Installation guide changes
The installation guide now distinguishes native source execution, Docker Compose, and the planned npm installer. Daily development uses native Teloa and Harness processes with Docker PostgreSQL. Full-container Compose remains an optional server deployment and testing path, building its image from source without requiring OrbStack.
The npm plan uses native execution with Docker PostgreSQL by default and an existing local dedicated database as a planned alternative. The installer has not been implemented or published. These docs now explain where files and programs are used, the permission boundaries, and which environments to use for development and release acceptance. Planned commands are not presented as available features.
Verification limits
These docs do not claim that every operating system, fresh machine, external model combination, or mainland China network environment has been tested. Check the installation requirements for your environment. If something fails, record the version and error instead of overwriting work data.
Documentation builds and interaction checks are separate from product end-to-end tests. Readable documentation does not imply that every model behavior has a deterministic result.