Generated documents

The in-app Documentation Center (the Docs section) generates per-deployment documentation from the rows the platform already holds. Derived documents are never hand-authored and never stale: each one is rendered at the moment you open it, stamped with when it was derived. There is no generate button and nothing to keep in sync.

This is different from this docs site (help about using StackTakt) and from attestation documents (completed and approved by a person), which share the same Docs section.

The three document types

Document	What it covers	Available
System overview	What the deployment is: scope, key components and their hardening, the deployment record (who approved, when, what resources).	Always, per applied deployment.
Endpoint runbook	SFTP endpoints only: how partners connect (per-user commands), the data layout, key rotation, and teardown.	Once evidence has captured the server.
Control narrative	Every control the deployment asserts: citation, status, implementing resources, and caveats verbatim.	Once the control snapshot exists (first apply).

Every control narrative opens with the same statement: it describes capabilities the deployed infrastructure demonstrates, with citations to the HIPAA Security Rule, and does not assert a compliance status for any party.

The point-in-time counterpart

Derived documents always show the present. When you need a record that cannot change afterwards, use the evidence package: its PDF is the point-in-time, auditor-facing artifact, and re-captures write new packages rather than editing old ones.

Beside the documents

The Docs rail also links each applied deployment’s Evidence pack and lists the tenant’s attestation documents with their statuses, so the whole documentation story for a tenant lives on one screen.