Peak Docs · Context-aware documents
One document.
The right context.
Context-aware documents: customer, project and tasks appear in the text as real references. Automatic context detection is a preview, shown with an example.
Which change do you want to check?
Type @ and pick the customer, project or task. The text then holds a real reference, not a copied name.
One document,
one context.
- 01Reference
- 02Backlink
- 03Preview
A real story starts with its release.
What was hard before?
A project report names the customer as plain text, the tasks live elsewhere, and later nobody can tell which documents belong to which project. In Peak Docs you reference customers, projects and tasks with @, and the object points back to the document.
This pattern shows the structure. It doesn't tell a real customer case yet.
The path to change
Business context in three layers.
The reference
Type @ and pick the customer, project or task. The text then holds a real reference, not a copied name.
Customer and project as references in the textEvidence format · not filled in yetThe starting point.
In the original.Original excerptInsert the released passage here.
A / ObservationWhich concrete friction is visible in this source?Example · @ reference in a paragraph The backlink
From the project you see which documents mention it. Your team finds the report through the project, not through the file name.
Documents findable from the objectEvidence format · not filled in yetOne step.
Traceable.BeforeOriginal processSource evidence requiredChangeConcrete interventionProduct view and date requiredExample · backlinks on the project The preview
A document suggesting the right context by itself is a preview and not available today. You choose the context on purpose yourself.
Suggested context, as a concept onlyEvidence format · not filled in yetThe result.
With a yardstick.- Observation
- Not evidenced yet
- Period
- Open
- Source & release
- Pending
Without released data this statement stays open.
Preview · context suggestion, not available
What can be evidenced
What you see while writing.
The evidence is still pending
No proven results yet. Peak Docs shows no figures here until real, released data exists.
The sculpture does not depict a customer.
One perspective.
With name and release.
Beyond the single case
What a good context document does.
Reference instead of copy
A customer or a project exists once. The document points to it instead of copying data that goes stale later.
Key ideaOne name, one source
Only what you may see
A reference shows only what you may see in the workspace anyway. Released context for outside readers is not part of it.
Key ideaContext with clear limits
What this article is based on.
Sample dossier with made-up data, not a customer story. @ references to customers, projects and tasks and backlinks exist in Peak Docs; automatic context detection is a preview and not available today.
- Editorial demo
Editorial example with made-up sample data. Co-editing, library and search, comments, versions, references to customers, projects and tasks, health signals and link sharing exist in Peak Docs today; everything else is marked as preview, concept or planned.
- Evidence pending
No released Peak Docs customer story. No customers, quotes or results are shown.
Write with the context, not next to it.
Create your first document and use @ to reference the customer and the project it is about.
Frequently asked questions
Does Peak Docs detect the context automatically?
Not yet. Automatic context detection is a preview. Today you reference customers, projects and tasks yourself with @.
What is a backlink?
The object you reference points back to your document. Your team finds the report through the project.
Are the customers on this page real?
No. The sample project and all names are made up.



