Read less
Context-aware block fetching
Agents shouldn't have to re-read entire documents just to advance a single task.
Documentation for the Agent Era
The surface where human intent meets agent execution.
Nyxdoc is building a calmer documentation system for teams that already feel the pressure of agent work. Readable structure, bounded change, and durable review should live in the product itself — not in scattered process glue.
Change safely
Turn writing into bounded, reviewable patches
Good execution means scoped edits, explicit intent, and change history that stays inspectable.
Keep trust
Make history and rollback part of the interface
Confidence comes from seeing what changed, why it changed, and how to recover if needed.
Why this matters now
Documentation for humans and agents.
As agents move into implementation, review, and operations, the bottleneck shifts from raw model output to context quality. Weak structure creates noisy handoffs. Strong structure turns documentation into a dependable working surface.
Pressure
Agents are no longer just an experiment
They are entering real delivery loops, but most docs still assume patient human reconstruction and implicit context.
Breakage
Static pages trigger redundant context loading
Whole-page rereads, vague scope, and missing revision boundaries make every automation loop more expensive.
Shift
Execution quality starts with document quality
Teams win when intent, revision state, and handoff continuity stay legible across humans and agents.
Outcome
Knowledge becomes operational, not archival
Documentation should support action, review, rollback, and continuity instead of ending at explanation.
What Nyxdoc is building
An agent-first document operating model.
We are not trying to make a prettier wiki. We are building a document system where reading, writing, and review each have a visible contract.
Read
Manifest-first context loading
Start from structure, then fetch only the block-level context needed for the task at hand.
Write
First-class patch and commit workflows
Changes should be bounded, attributable, and revision-aware rather than hidden inside a full-page rewrite.
Review
Comments that carry scope and status
Discussion becomes a bridge from human instruction to agent execution and back to calm review.
What the product has to preserve
Transparent work, effortless oversight.
We care about tools that let teams delegate narrow work confidently: explicit boundaries, durable history, and a review experience that does not require reconstructing everything from memory.
Control
Trust comes from visible change
Diffs, rollback, and attribution are not admin extras. They are the core product surface for agent collaboration.
Handoff
Context should survive across sessions and contributors
The system should remember intent, scope, and revision state so the next human or agent starts from clarity.
Restraint
Human judgment stays explicit at the right moments
Agents execute bounded work. People define direction, review outcomes, and keep operational control.
“The future is not documents that agents can merely read. It is documents that let human judgment and agent action stay connected without losing trust.”
Where this is going
Start from a practical execution loop.
A person leaves a scoped instruction. An agent reads the minimum necessary context. A bounded patch comes back for review. The system keeps the resulting state durable.
Foundation
Addressable structure and revision-aware history
Block-level addressing, partial fetch, and a document model that can hold durable operational memory.
Workflow
Comments that connect intent to execution
Discussion becomes structured work intake instead of a side channel with missing status and scope.
Confidence
Review, rollback, and attribution built in
Trust grows when teams can inspect what happened and recover cleanly without extra process glue.
Early conversations
If this already feels like your workflow problem, we should talk.
We want to hear from teams where agents are active in implementation, review, or operations — and where the current document layer is starting to break under that load.