Xtrable
Architecture documentation rots because the words and the facts are written by the same hand at the same time, and only the words get revisited. NeoArc separates the two. You write the narrative. The facts come live from the model.
Live facts, embedded in prose
Drop a live element into a page and it stays bound to the model: how many entities are active, which fields carry sensitive data, what has drifted, entities grouped by status. It can render inline inside a sentence as a figure, or as a block: a headline number, a table, or a chart. When the architecture changes, the element re-resolves. The page updates itself.
The end of "is this still accurate?"
Because the facts are queries against the live model rather than numbers typed in once, a document cannot silently disagree with the system it describes. The reader stops wondering whether the page is current, and the author stops dreading the next review cycle. Accuracy becomes the default, not a chore.
Decisions, recorded properly
NeoArc includes architecture decision records as a first-class document type, with a simple ladder from a quick one-paragraph note to a full multi-option write-up, so a decision gets exactly as much rigour as it deserves. Decisions live alongside the model they affect, and link to it, so the reasoning behind the architecture is never lost.
Everything links, and links never break
Pages, diagrams and decisions all link to one another by stable identity rather than by file path, so a link keeps working even when its target is renamed or moved. Your documentation becomes a connected body of knowledge, not a pile of files that slowly stop pointing at each other.