Idolum Inspect the evidence

Idolum performs bounded AI-assisted work inside the systems your team already uses.

Continue to work as you perform best.

Scope, permissions, evidence, approvals, and a stop condition are declared before execution begins. The customer retains authority.

Discuss one bounded workflow
See the work

01 / The work

Useful work, bounded from discovery to handback.

Idolum recovers inherited systems, builds new capability, operates controlled processes, and returns code, evidence, procedure, and authority to the customer.

01

Recover

Work
Map an inherited production system, stabilize its failure path, and leave an inspectable operating record.
Boundary
Read-only discovery precedes staged mutation. A named recovery path remains open.
02

Build

Work
Add a bounded capability inside the customer’s existing tools and definition of done.
Boundary
Customer controls, review paths, acceptance criteria, and approval gates retain authority.
03

Operate

Work
Run a recurring cross-system process, including its exception and approval paths.
Boundary
Permitted actions, audit trails, escalation, and stop conditions remain explicit.
04

Hand back

Work
Transfer code, evidence, procedure, and operating knowledge to the customer.
Boundary
Authority returns to the customer. Continued dependence is not an acceptance condition.

Private engagement evidenceAttribution standard: companies and individuals are named only with explicit approval. Private records substantiate engagements; the public evidence method makes implementation claims inspectable without pretending to prove customer outcomes.

02 / Authority

Authority does not expand just because the work continues.

A declared world is the tools, data, permissions, and network surfaces available to one task. The customer defines that world before execution and retains approval, escalation, and revocation.

  1. Declare

    What may the task access, and what remains forbidden?

  2. Execute

    Which tools and actions are assigned to this outcome?

  3. Observe

    What evidence shows progress, transfer, and exception?

  4. Decide

    What counts as done, and who approves escalation or stop?

  5. Hand back

    How do code, procedure, evidence, and authority return?

The loop does not earn more authority by continuing to run.

Containment exampleIdolum treats prompt injection first as a containment problem. Detection remains one layer; isolation limits what compromised context can reach. When a path is judged compromised, execution there stops. Recovery proceeds only through a separately authorized route.

03 / Inspectability

The methods are public. Customer particulars stay protected.

Public instruments and implementations expose how the posture is tested and built. They support mechanism and method claims—not private customer outcomes.

Idolum is absolutist about one thing: knowing where context integrity fails.

Experimental evidence

Spectral Faithfulness

An experimental instrument studies whether models maintain context, identity, and information boundaries under declared conditions.

Limit: the instrument does not monitor a deployment, certify containment, or prove immunity from prompt injection.

Public · MIT · snapshot refreshed
Read the methodRun the promptsInspect limitations
Method documentation

Aphelion

Harness lineage for explicit authority, environment, execution, and recovery.

Public · Apache-2.0 · updated Read the authority model
Mechanism evidence

Engram

An operator-visible route from familiar messaging to explicitly addressed terminal work.

Public · MIT · updated Read the data flow
Mechanism evidence

Kenogram

A container contract that declares mounts, networks, secrets, resources, and lifecycle.

Public · MIT · updated Read the execution boundary

Repository facts come from a validated, source-controlled public snapshot. Read how the snapshot is refreshed and bounded.

04 / A bounded beginning

Name one world. Define one outcome. Keep one honest stop condition.

Start with one workflow. Map what it may touch, define the outcome, agree on what evidence counts, and decide when it stops.

Discuss one bounded workflow