Founder-led written practice

RGRA exists for the point where a critical record must support what comes next.

The practice is deliberately narrow: one decision or reliance question, one agreed record boundary, one stated cut-off and one controlled written outcome.

Why the discipline exists

Critical project files are rarely empty. The difficulty appears when approvals, minutes, reports, conditions, changes and later summaries were created for different purposes or dates and a new decision needs to know exactly what the agreed record supports now — or what it supported then.

RGRA was built to isolate that documentary question before the next authorised judgement is applied.

Written-first

Questions, scope, cut-off, record boundary, findings and release conditions are fixed in writing so the work can be checked and reproduced.

Source-controlled

Material statements are traced back to the agreed record. Qualifications, contrary material and source inconsistencies remain visible.

Founder-controlled

Thanasis Lagoudakos controls matter acceptance, scope, analysis and release. Specialist judgement remains with the authorised professional function when triggered.

Operating posture

The objective is not to produce a stronger narrative. It is to state the narrowest written position the agreed record can support.

Where the record is sufficient

The File-Position Note states the supported position and preserves the qualifications that must travel with it.

Where it is not

The output states the limitation, unresolved point or non-determinability rather than filling the gap with assumption.

RGRA does not add a parallel workstream where an accountable process already provides the required source-supported position for the same decision and use.

Start safely

Begin with a short, non-sensitive written background.

Start with a written fit check