Engineering Principles

The permanent technical philosophy of Fortivant.

Evidence. Understanding. Action.

These principles govern how Fortivant is built. They are distinct from the Constitution, which governs how the platform reasons, and from the Manifesto, which declares why the platform exists.

  1. Principle 01

    Law of Evidence

    Every claim traces to a source. Nothing is asserted without provenance. Evidence records are versioned and preserved across supersession.

  2. Principle 02

    Law of Uncertainty

    Confidence is stated numerically. Unknowns are named openly. Missing evidence is surfaced as an actionable gap, never hidden behind implied precision.

  3. Principle 03

    Deterministic Reasoning

    Engines are deterministic. The same inputs produce the same conclusions, always. Rubrics and engine versions are pinned to every snapshot.

  4. Principle 04

    Confidence

    Every conclusion is accompanied by a confidence value derived from the underlying evidence — never guessed, never rounded away.

  5. Principle 05

    Explainability

    Every recommendation traces to criteria, rubric version, and evidence. Reasoning paths are inspectable end-to-end.

  6. Principle 06

    Versioning

    Rubrics, engines, snapshots, facts, records, and recommendations carry versions. Nothing is silently rewritten.

  7. Principle 07

    Append-only History

    Superseded records remain queryable. History is never lost; it is layered.

  8. Principle 08

    Human Oversight

    Fortivant informs decisions. Leaders make them. The platform never removes human judgment from consequential outcomes.

  9. Principle 09

    Security by Design

    Tenant isolation, private document storage, signed URL access, and least-privilege service roles are foundational — not features added later.

  10. Principle 10

    Evidence Provenance

    Provenance flows through relational junction tables — one canonical path from evidence to conclusion, never duplicated caches.