PTD CAPITAL LLC
PTD-ARC-2026-001
CONTINUOUS REPORTING RELEASE NOTE
Original record date: 12 January 2026
Recorded author: Systems & Data
Reconstructed edition: 16 October 2026 / Version 2.0 / Open

01 / Reporting perimeter

The institutional history records the introduction of continuous portfolio reporting and the opening of the archive in 2026. This reconstructed release note describes the current information flow and the controls added in the October revision. It does not represent the current implementation as software already delivered in January.

The central register links projects, responsible people, workstreams, operating events, indicators, publications and documents. Editorial placement is recorded separately from financial inclusion. Registering a development project may change which files appear on the site without adding a financial value or altering an accepted reporting perimeter.

02 / Publication sequence

A publication begins with dated evidence. The selected project, workstream state and period boundary determine which observations can be used. The system checks identifiers, dates, units and access before preparing a release. A short operating update has a different content boundary from a long research article or quarterly review.

The catalogue and home page read the current accepted register. An earlier report retains its frozen narrative, charts and supporting period records. Regenerating its PDF must not replace those records with the latest mutable project state. A correction produces a new version and preserves the preceding issue.

03 / Access and failure

Access is enforced before content leaves the server. Public responses may contain a restricted document's title, summary, author, date and contents, but not its full narrative, account schedules or attachment. The same restriction applies when an operating note also appears inside another source field.

A publishing cycle either accepts its validated changes together or leaves the prior accepted state intact. A failed export, invalid publication or unsuccessful PDF generation must be recorded as a failure. A scheduler being installed does not establish that its most recent cycle succeeded. The dashboard distinguishes the last successful run, recent errors and whether publishing is paused.

04 / Revision evidence

Validation uses an isolated copy of the register. Tests of weekly, monthly and quarterly cycles do not become operating events in the live chronology. The revision record retains the accepted document version and the reason for a change. This separation keeps test activity, proposed work and published operating history from being conflated.

Sources: institutional history, 2026 entry; central project, publication and snapshot schemas; private-access and automation validation records. October implementation controls are described as current revisions, not backdated delivery claims.