Nyxdoc exists because teams are about to work with agents every day, yet most documentation is still written as static pages for human eyes only. We are designing a new kind of documentation system: one that humans can trust and agents can act on precisely.
Nyxdoc is shaping a calmer surface for human judgment and agent execution to meet.
The next wave of software work will not be just “people using docs.” It will be humans, coding agents, operators, and workflows all reading from the same source of truth. If that source of truth is vague, overlong, or structurally weak, every handoff gets more expensive.
They are moving into implementation, operations, review, and documentation upkeep. But the document layer they depend on is still mostly passive and underspecified.
The teams that win will not just have better models. They will have better structure for intent, revision history, and handoff continuity.
They help people browse, but they do not give agents a reliable contract for partial fetch, scoped edits, intentful comments, or safe completion loops.
As agents move from chat experiments into real work, documentation must expose stable blocks, revision boundaries, and explicit task scopes.
Good documentation should not only explain what a team knows. It should support action, review, rollback, and continuity across sessions.
We are not trying to make a prettier wiki. We are building an agent-first document operating model where reading, writing, and discussion all become structured contracts.
Start with lightweight structure, then fetch only the blocks required for the task. Less waste, less confusion, more precision.
Agents should propose bounded, auditable changes with preconditions and revision history, not rewrite a whole page and hope for the best.
A comment should carry scope, intent, priority, and status, forming a bridge from human instruction to agent execution and back to review.
We believe the winning product is not the one that pretends agents are perfect. It is the one that makes agent work inspectable, recoverable, and calm.
Diffs, rollback, and audit trails are not secondary admin tools. They are the core UX that allows people to let agents do real work.
People define direction and approve outcomes. Agents handle narrow execution against stable document contracts.
Handoffs between teammates, sessions, and agents should cost less over time because the system remembers structure, intent, and history.
Runbooks, ADRs, product decisions, and implementation context are not side notes. They are the operating system of modern software teams.
Nyxdoc starts from a practical loop: a person leaves a scoped instruction, an agent reads the minimum necessary context, submits a verifiable patch, and the team reviews the result with confidence.
We are interested in teams who are already feeling the friction between human intent, agent execution, and documentation that cannot carry the load.