Skip to content
Janus
Menu

03 / WHERE IT APPLIES

Workflow structure / not industry

Janus fits work where the same professional works with AI repeatedly — and reality eventually answers back.

The best way to locate Janus is by workflow structure rather than industry.

A suitable workflow gives Janus enough repeated evidence to learn how a particular professional and AI work together, enough freedom to change that interaction, and enough outcome feedback to find out whether the change helped.

The product is defined by those conditions, not by a vertical.

01 / Fit test

Five conditions

Structural fit

All five conditions

01

Continuity

  • Case
  • Case
  • Case

The work repeats with enough continuity

Janus needs recurring cases involving the same professional and a sufficiently stable Human+AI pairing.

The cases do not have to be identical, but they have to recur often enough for the system to distinguish a one-off event from a pattern — and to test whether that pattern still holds later.

A single decision can be important. It cannot by itself support a longitudinal model.

02

Both sides matter

  • AI incidental
  • Both can change outcome
  • AI reliably completes alone

Both the person and the AI can affect the outcome

Janus is about the relationship between two decision-making components.

If AI is only incidental, there is little Human+AI interaction to learn from.

If the AI already completes the work reliably on its own and human judgment adds nothing, the useful answer may simply be automation.

Janus matters in the middle: where both sides can still change what happens.

03

Adaptable interaction

  • timing / presentation
  • support / challenge
  • another reviewer
  • human step remains / changes

The interaction can change

Learning only matters if the next case can be handled differently.

The workflow needs some real degrees of freedom: when and how the AI presents its view, how much support or challenge it provides, whether another reviewer is involved, and whether the human step remains necessary at all.

Janus needs something it is allowed to adapt.

04

Material cost

  • Too much review
  • Allocation matters
  • Too little independent judgment

Getting the division of thinking wrong has a material cost

Too much human review can waste scarce expert attention and erase the productivity gain from AI.

Too little independent judgment can leave important model errors without a useful backstop.

The exact cost can be time, money, risk, missed errors, unnecessary escalation, or expertise spent where it adds little.

The problem has to matter enough for a better allocation to be worth learning.

05

Adjudication

Strictest condition

  • Decision
  • Delay / noise / partiality
  • Later outcome

Quality + latency set learning speed

The outcome is eventually adjudicated

Someone or something eventually has to tell the system what actually happened.

This is the strictest condition.

Without later evidence, a Janus hypothesis can sound plausible but cannot lose. A prediction cannot be tested, and longitudinal inference turns into storytelling.

Adjudication does not have to be immediate or perfect. Outcomes can be delayed, partial, noisy, or probabilistic.

But their quality and latency determine how quickly Janus can learn.

Reality has to answer back often enough for the model to be wrong.

Five conditions, all of them required. The fifth is the strictest: without later evidence a hypothesis can sound plausible and never be wrong, which is the one failure a longitudinal system cannot survive.

02 / Economic fit

Where the fit is strongest

The economic case becomes especially strong when expert attention is scarce, errors are asymmetric or expensive, AI is already doing a meaningful share of the cognitive work, and the organization cannot simply choose "always review" or "always automate."

Economic amplifiers

Not fit conditions

  • expert attention is scarce
  • errors are asymmetric or expensive
  • AI is already doing a meaningful share of the cognitive work
  • cannot simply choose "always review" or "always automate"
Four things that strengthen the economic case where the structural conditions already hold. None of them is a condition, and scarce expert attention least of all.

Examples can include:

Examples / not deployments

  • security incident investigation;
  • fraud and AML alert review;
  • quality inspection and failure review;
  • trust and safety escalation;
  • some regulated expert-review workflows;
  • other repeated decisions where a person and AI both affect the result and useful outcome feedback eventually returns.

NOT DEMONSTRATED

No external deployments

This is a fit test, not a list of Janus deployments. There are no external deployments yet.

Constraint / required human review

Some workflows also impose human-review requirements independently of what Janus would learn. In those settings, the system cannot choose every possible degree of automation, but it can still adapt how the required human step is used.

03 / Worked instance

BEING BUILT

First worked instance: security incident investigation

Security investigation is the first workflow being built around the Janus mechanism because the structural conditions are unusually clear.

Cases recur. Analysts work repeatedly with AI-assisted tools. Expert attention is expensive. A missed incident and a redundant escalation do not have the same cost. And investigations eventually produce enough follow-up evidence to test at least some earlier judgments.

BEING BUILT

Worked instance

Fit condition

What it looks like here

01 / Continuity

The work repeats with enough continuity

Cases recur.

Analysts work repeatedly with AI-assisted tools.

02 / Both sides matter

Both the person and the AI can affect the outcome

Across repeated investigations, Janus can learn where an analyst's judgment changes the result.

03 / Adaptable interaction

The interaction can change

Those patterns can change how the next case is handled.

04 / Material cost

Getting the division of thinking wrong has a material cost

Expert attention is expensive.

A missed incident and a redundant escalation do not have the same cost.

05 / Adjudication

The outcome is eventually adjudicated

Investigations eventually produce enough follow-up evidence to test at least some earlier judgments.

Security was chosen because it satisfies the five structural conditions unusually clearly. The mapping is the reason for the choice, not a result from a deployment.

Across repeated investigations, Janus can learn where an analyst's judgment changes the result: which model errors they catch, how reliance changes, what kinds of evidence change their mind, when challenge helps, and when review stops adding useful signal.

Those patterns can change how the next case is handled.

For example, Janus can:

Degrees of freedom

Not a sequence

  1. 01change when and how the model presents its conclusion;
  2. 02introduce a counterargument or alternative explanation when challenge is useful;
  3. 03provide more or less guidance as the situation changes;
  4. 04route a case to a second reviewer or escalation;
  5. 05reduce or remove the human review step where it repeatedly adds little value.
Five things the system may do differently on the next case. They are alternatives, not stages, and reducing the human step is one of them rather than a failure of the others.

Same AI. Same kind of incident. Different analyst — or the same analyst later — and potentially a different right way to run the case.

Security is the first concrete workflow being built around these conditions.

04 / Does not fit

Where Janus does not fit

Breaks / 01 continuity

One-off or weakly comparable decisions

A merger, a unique reorganization, a singular strategic choice.

There may be no meaningful sequence of comparable cases in which a hypothesis can be tested and revised.

Breaks / 05 adjudication

Work with no usable adjudication

If nobody can establish what actually happened — even imperfectly — Janus has no reliable way to distinguish a good hypothesis from an attractive story.

This rules out more work than the other conditions do.

Breaks / 03 adaptability

Work where the interaction cannot change

If policy or tooling fixes exactly how the person and AI must work together, Janus may be able to observe the relationship but has little useful action to take.

Breaks / 02 both sides

Work where one side of the pairing is irrelevant

If AI is not materially involved, there is no Human+AI relationship to manage.

If AI can complete the work correctly on its own and the human adds no required or useful judgment, adding Janus is unnecessary.

Breaks / 04 material cost

Work where the problem is too cheap

If redundant review costs almost nothing and mistakes in the handoff have little consequence, learning a better allocation may not justify another system.

05 / Structural boundary

The boundary is structural

Security is the first place the broader mechanism is being made concrete.

The category itself is structural rather than industry-specific.

Does the same professional work with AI repeatedly, can the division of thinking change, does getting that division wrong matter, and does reality eventually provide enough evidence to learn from it?

  • Repeated Human+AI work
  • Division can change
  • Wrong division matters
  • Reality returns evidence

If yes,

Janus may have something to learn.

If not,

it probably does not belong there.

egor@janusstaff.com