Skip to content

    Faciens Technologies

    Compile, verify and govern AI agent plans.

    AI agents now issue refunds, change accounts and move money, and nobody can prove beforehand that an action was allowed. The FACIENS Trajectory Compiler can.

    For
    Any organization letting AI agents take actions under rules: finance and billing, customer operations, IT and security, compliance, and beyond.
    Why now
    Agents now execute multi-step plans with write access to production systems. Prevailing controls (prompt guardrails, model-graded checks, post-hoc logs) are probabilistic and judge one step at a time; they do not prove a whole plan complies before it executes, the evidence of control that frameworks like the EU AI Act increasingly demand.
    Why Faciens
    Plans are compiled against declared rules, not guessed: each one satisfies every constraint, or the compiler names the rules in conflict. A separate verifier, sharing no code with the compiler, replays every plan and issues a hash-bound certificate an auditor can check. Working software: 191 automated tests, a versioned API and an audit trail.
    faciens: billing-dispute demo
    Replay of the synthetic billing-dispute demo. Outcomes are the demo's real results; the hash is computed in your browser.

    The product

    Layer 02

    The FACIENS Trajectory Compiler: give it a workflow's rules, and it returns only the plans an agent is allowed to run, each with an independent proof. Scroll to watch it work.

    FACIENS Trajectory Compiler

    Unlike tools that let a model propose a plan and check it afterwards, the Trajectory Compiler only returns plans that satisfy every declared rule, and every plan is verified independently before it runs.

    1. State spaceMany possible paths through a workflow's states. Most are wrong in ways no rule has named yet.
    2. ConstraintsDeclared rules (approvals, limits, deadlines, forbidden actions) mark states as forbidden. Each path is cut at its first violation.
    3. CompilationA bounded search expands only through permitted states.
    4. TrajectoryA feasible path emerges. When none exists, the compiler names the conflicting rules instead.
    5. VerificationAn independent checker, sharing no code with the compiler, replays every step.
    6. CertificationProblem, plan and evidence are bound into a hash-linked certificate.
    7. ExecutionThe certified plan runs under the execution runtime, which watches for divergence.

    A toy example, computed live in your browser.

    What exists today

    191automated tests passing across the compiler, verifier, runtime and API
    0.942AUC separating approved from failed runs with whole runs held out, in a controlled synthetic evaluation (95% interval 0.933 to 0.951)
    0.782AUC detecting unsafe agent runs on ATBench, a third-party benchmark of 1,000 runs, from safe examples only (±0.017 over 10 seeds)
    End to enda working billing-dispute demo: compiled, verified, monitored and gated

    Pre-seed, with no customers yet. We are recruiting two or three design partners for a ten-week evaluation on one real workflow.

    The platform it unlocks

    Ten more tools on the same engine, from monitoring execution to gating a release, alongside the OLPW governance stack. Select any one to see it running.

    Move to turn the system. Drag to rotate. Select any product.

    Governance stack

      Engine

        Instruments

          Building Future Frontiers

          Faciens

          Layer 03

          From the Latin faciens: making, bringing about.

          Faciens Technologies builds the FACIENS Trajectory Compiler, which checks what AI agents plan before they act, and the platform around it, from monitoring execution to gating a release, alongside the OLPW governance stack.

          Founder
          Arcades Cinza
          Based in
          Kingston, Jamaica
          Focus
          Verifiable control for AI agents
          Stage
          Pre-seed, pre-revenue
          Product
          FACIENS Trajectory Compiler

          Collaborate

          Design partners, investors and engineers: write to the founder.