Skip to content
Janus
Menu

01 / HOW IT WORKS

Janus learns how a professional works with AI over time.

Most AI systems optimize the task in front of them: better answers, faster work, more automation.

Janus also learns the human side of the workflow, because repeated AI assistance can change what people keep doing themselves.

It works with the same professional over time, learns from how they reason with AI, and uses that history to adapt the next interaction.

The aim is not to preserve human involvement for its own sake. It is to keep human judgment active where it still has value — and automate where it does not.

01 / Ordinary work

Learn from ordinary work

Janus is designed as a persistent professional counterpart, not a recurring assessment.

A professional can ask a question, test a hypothesis, explain why evidence matters, disagree with the model, revisit a past case, or reason through uncertainty.

Across that history, Janus builds a private, revisable model of how this professional works with AI. It can learn:

SCHEMATIC

Ordinary work produces evidence

Useful work

  • ask a question
  • test a hypothesis
  • explain why evidence matters
  • disagree with the model
  • revisit a past case
  • reason through uncertainty

Context

  • person
  • task
  • model
  • interaction history

Private, revisable model

  • what evidence the person considers sufficient;
  • how they express uncertainty;
  • how well confidence tracks outcomes;
  • what tends to change their mind;
  • where they rely quickly on AI;
  • which model errors they tend to catch;
  • how they respond to challenge, guidance, or disagreement.
Ordinary work produces evidence; each finding stays bound to the person, the task, the model and the history it came from; together they form a model Janus can revise rather than a fixed description of the person.

Each finding stays tied to context: a particular person, task, model, and interaction history.

Its value is practical: can it choose a better way to work with this person next?

02 / Trajectory

Track what changes over time

AI can take over work where human involvement no longer adds value. That is often exactly what should happen.

The harder case is when the organization still depends on human judgment for rare failures, ambiguous cases, or higher-order decisions.

Then today's performance is not the only question.

SCHEMATIC

Repeated cases

  1. Case 01
  2. Case 02
  3. Case 03
  4. Case 04
  5. Case 05
  • reliance changes
  • calibration shifts
  • still catches model misses
  • review stops adding useful value

Are we still exercising the human judgment we depend on?

Across repeated cases Janus watches four qualitative things: how reliance changes, how calibration shifts, where the person still catches what the model misses, and where review has stopped adding value. The marks are illustrative registration, not measurements.

Janus keeps that trajectory in view: how reliance changes, how calibration shifts, where the person still catches things the model misses, and where review has stopped adding useful value.

The distinction is between useful delegation and quietly losing a human backstop the workflow still expects to have.

03 / Action space

Change how much of the thinking AI does

Janus uses that history to adapt the next interaction.

Depending on the person, task, recent history, and current conditions, it can:

SCHEMATIC

Not a sequence

  1. 01give the answer directly;
  2. 02let AI draft and ask the person to verify;
  3. 03show the evidence before the conclusion;
  4. 04ask the person to form a hypothesis first;
  5. 05challenge the reasoning or ask for an alternative;
  6. 06use a case as deliberate practice;
  7. 07remove scaffolding when it is no longer useful;
  8. 08add support when the person is overloaded;
  9. 09debrief after the outcome is known;
  10. 10recommend full automation where human involvement no longer earns its cost.
Ten ways the next interaction can be run. They are alternatives available to Janus, not stages of a process, and no order among them is implied.

Janus can ask for more independent thinking, make the work easier, or remove the human step entirely.

The division of cognitive work is something to adapt, not set once for a role.

04 / Later evidence

Learn from what happens next

Janus keeps a history of what it believed, how it adapted the interaction, and what happened next.

SCHEMATIC

Belief, expectation, outcome, revision

  1. 01Hypothesis / v1
  2. 02Expectation
  3. 03Adapted interaction
  4. 04Later case / outcome
  5. 05Confirm / contradict / unresolved
    • Confirm
    • Contradict
    • Unresolved
  6. 06Revised model / v2v1 retained in history
Janus holds a hypothesis, which owes an expectation about what a different way of working should produce. The interaction changes, a later case arrives, and the expectation is confirmed, contradicted or left unresolved. The model is revised, and the earlier version is kept rather than discarded.

A useful hypothesis should imply something about what Janus expects to see after a different way of working together. Later cases and outcomes can confirm that expectation, contradict it, or leave it unresolved.

As that evidence accumulates, earlier hypotheses can strengthen, weaken, or be replaced.

The result is a continually revised model of where this professional and this AI work well together, where they do not, and what kind of assistance helps next.

05 / Boundary

Keep the deeper model private

The professional-facing relationship can be richer than the information the organization needs.

Janus separates the private adaptation model from the organization-facing operational layer.

Inside Janus, the response layer can work from bounded behavioral guidance rather than raw internal labels, scores, or model mechanics.

The private side can hold detailed hypotheses about reasoning, calibration, reliance, blind spots, and responses to different kinds of assistance.

The organization-facing side can receive the operational output it needs: whether an independent check is required, another review or escalation is warranted, a review step is no longer useful, more automation is appropriate, and how the workflow is changing overall.

SCHEMATIC

Private adaptation model, bounded guidance, operational output

Private adaptation model

  • reasoning
  • calibration
  • reliance
  • blind spots
  • responses to assistance

Private

Raw internal model does not cross

Bounded behavioral guidance

Organization-facing operational layer

  • whether an independent check is required
  • another review or escalation is warranted
  • a review step is no longer useful
  • more automation is appropriate
  • how the workflow is changing overall

Operational

The private side holds detailed hypotheses about how the professional works. Only bounded behavioral guidance crosses the boundary; what reaches the organization is operational output about the workflow, not the model Janus uses to adapt.

The organization does not need access to the internal model Janus uses to adapt to the professional.

That separation also protects the interaction itself. If ordinary reasoning with Janus becomes a performance dossier, people have a reason to stop reasoning openly with it.

06 / Longitudinal

The longitudinal idea

A static workflow asks:

Who should do this task?

Janus asks:

Who should do which part of the thinking now — given what has happened between this person and this AI so far?

The answer can change.

So Janus keeps learning.

What runs today