Evidence-first, by construction.
FLOSMOSIS systems share one operating philosophy. These are the safeguards we design in — described as we have built them, without claiming certification we do not hold.
Source grounding and provenance
Work is prepared from source facts, and the provenance is kept alongside it so any prepared item can be traced back to where it came from.
Bounded AI assistance
AI extracts, organises, checks, summarises and drafts. It does not make legal, governance, conflict, filing or payment decisions.
Human approval and verification gates
Consequential and outbound action waits behind an accountable person. In BarristerOS, extracted dates stay proposed until a barrister verifies them.
Tamper-evident histories where implemented
Where a system seals records — as Flostruction does for approved shifts — the history is append-only and tamper-evident, so a change cannot happen without leaving a trace.
Fail-closed behaviour
When a capability is unavailable or a check cannot be completed safely, the system holds rather than proceeds.
Domain workflows, not a generic wrapper
Each system is a workflow for its domain, with evidence and human control designed in — not a thin layer over a model.
We describe what is designed and implemented in the product. We do not say “compliant”, “certified”, “unhackable” or “guaranteed”.