Evidence that outlives the project

When a project ends, the duty to prove does not. Archive is meant to turn the closing into a lasting state: readable, exportable, unchangeable. This line is in planning and not built yet.

Lasting state

Closed is not deleted

Next to active and suspended, a third state is meant to appear: archived. With no deletion clock running, and with read access and search for permitted roles. The way back into the active state should be possible and logged.

What is planned

Write lock

One lock at the entrance

Instead of many separate rules, one central lock is planned: for an archived project every writing path should refuse, with a clear message in the content languages.

What is planned

Integrity

A check every year

A yearly run is planned that holds the checksums of the evidence chain against the originals and files the result as a report with a timestamp. If something deviates, it should be reported rather than passed over in silence.

01What is planned In planning

What is planned

This is the state of the plan, not the state of the software. It gets built after the beta.

Archived state

A lasting state with no deletion clock, next to active and suspended.

Read, search, export

Permitted roles should still read, search and pull exports.

Central write lock

One gate at the entrance instead of a separate rule per table.

Yearly integrity report

One report per archived project, timestamped through the existing mechanism.

Cold storage without rework

Originals should stay byte identical; only the storage class gets cheaper. Retrieval from cold storage can take minutes.

Reactivation

The way back into the active state should be documented and traceable.

Archive is reading. Deadlines, inspection cycles and reporting paths after handover belong to the Operations line. This page describes a plan and says nothing about approval or legal effect.

02Trust register

Trust register

Evidence over rank: every step from the spoken word to approval stays traceable, while a suggestion never takes effect on its own.

01Capture

02Structure

03Prove

FIDICVOBJCTAIAConsensusDocs

FIDIC, AIA, ConsensusDocs, JCT, VOB and custom frameworks are versioned. Chops, hanko, dojang and company stamps are recorded only as technical confirmations, with no claim of special legal effect.

A continuous evidence chain

Conversation, transcript, suggestion and human decision form a continuous chronology that is never silently overwritten.

Fair to both sides

Before evidence protects client and contractor alike. Companies can challenge scorecards; site management records the decision.

03Language

Rendered daywork report containing German, Chinese, Japanese, Korean, Thai and Hindi text

Reports in every script

Embedded Noto fonts render Chinese, Japanese, Korean, Thai and Devanagari correctly in PDF reports.

Register interest in Archive

Archive gets built after the beta. If you want to bring in the requirements from your own portfolio, get in touch now.