Technical information and document systems
Systems that keep technical documents and standards correct over time, with the change to each one planned before it is applied.
Identification
Established. Demonstrated by two or more published systems, so the pattern is repeated rather than singular.
Repeatable outcome
Document and standards systems where a change is proposed, inspected, and only then applied — and where the previous state is still available afterwards.
Technical documentation decays in a specific way: it is edited by hand, in bulk, under time pressure, and the damage is only noticed later. The structure that prevents it is the same each time. The corpus has a schema, conformance is checked rather than assumed, a bulk change is planned and shown before it touches anything, and there is a restore path for the case where the plan was wrong.
That makes documentation something a repository can be held to, rather than something that is true on the day it is written.
Scope and boundaries
The evidence is a document-maintenance tool and a versioned standards system. Both are about keeping a body of technical text correct mechanically; neither is about writing it.
This does not imply:
- Content authoring, editing, or technical writing as a service.
- Records management, retention, or compliance advice. These systems have no legal or regulatory retention role, and nothing here should be read as advice about one.
- Migration of anyone else’s corpus. No such engagement exists.
Evidence systems
Published systems that demonstrate this capability, derived from those records rather than asserted here.
L3D-SYS-004
Project Standards
Versioned standards with schemas, adoption mechanisms, validation, and drift gates that a repository can be held to.
Open source under Apache-2.0, with versioned releases. Read the source and adopt it directly.
L3D-SYS-005
docmend
A document maintenance tool that separates scan, plan, apply, verify, and restore, defaults to a dry run, and can resume after interruption.
Open source under MIT, with published releases. Install it or read the source.
L3D-SYS-012
Agent Pseudocode
A pseudocode convention for instructing agents, with a validator, a formatter, and a language server so the convention is enforced rather than remembered.
Open source under MIT. The source is readable and runnable; there are no published releases.
Active offerings
None. This capability describes work that has been done, and nothing on this site is for sale today. If that changes it will appear on the availability page as a record with its own scope and exclusions.
Related records
The capability index lists the rest. What can actually be obtained today is on the availability page, which is a different question from what has been demonstrated.