Workflow Scanner
システムログから実際のワークフローを再構成。自動化する前にボトルネック、判断ポイント、自動化機会を発見します。
価値と現実を、
同時にスキャン
価値だけではオペレーションは動かない。オペレーションだけでは最適化できない。
二軸スキャニングが判断と実行を同時にマッピング。
2つのスキャン、1つのモデル
得られるもの
2つのマップを並列表示。1つはあなたが言っていること。もう1つはあなたがやっていること。
Avg 42h legal bottleneck
Cost cited 2.3x more in approvals
"What the organization says it values"
"What the organization actually does"
Where these two maps diverge, MARIA OS detects structural risk.
One Scan, One Report
Values, reality, gaps, bottlenecks, and gate-validated recommendations — all in a single deliverable.
Stated vs Practiced alignment
Bottleneck wait time (hours)
Where values and reality diverge
Gate-validated actions
インタビューは最後に：意見より事実を先に
トレースを先に読む。人間に聞くのは最後。エビデンスからリアリティマップを構築。
Connect
- Read-only access
- Least privilege
- Audit log
- PII masking
“Connected to Slack, Jira, Google Drive with read-only OAuth”
Artifact Scan
- Parse documents & files
- Extract ownership chains
- Tag decision artifacts
“Found 847 documents, 12 ownership chains, 34 decision points”
Event Log Scan
- Timeline reconstruction
- Latency measurements
- Handoff detection
“Detected 4 bottlenecks: Finance review avg 14h, VP approval avg 22h”
Implicit Decision Detection
- Unwritten approval gates
- Shadow escalation paths
- Informal authority maps
“3 hidden gates: CFO informal veto, Team lead chat approval, Friday freeze”
Replay Interview
- Walk-through with owners
- Confirm or correct findings
- Fill evidence gaps
“Owner confirmed: 'Yes, nothing ships without Sarah's Slack thumbs-up'”
混沌を入力、構造を出力, Structure Out
現実のデータはデフォルトで非構造化。MARIA OSがそれを監査可能でエビデンスに紐付いた構造に変換。
判断を統制し、実行を並列化
同じワークフローを2つのグラフに分割：意思決定用と実行用。
Graph Builder Output
Purchase Order Approval Flow
This is what your PO approval actually looks like. MARIA found 2 bottlenecks and 1 hidden gate between Risk Assessment and Budget Check.
Estimated cycle-time reduction: 42% after gate restructuring.
既存を最適化し、新規を作成
既存フローはより高速に。新規フローは安全にスタート。すべての変更はバージョン管理され監査可能。
Invoice Approval Workflow — as observed
Auto-extract invoice data
Route by amount
Parallel: Finance + Manager
Evidence auto-bundle
Invoice Approval Workflow — recomposed
記憶からグラフへ
MARIA OSはワークフローを置き換えない。理解し、構造化し、進化させる。
Current State
7 steps, 3 hidden gates, no audit trail
With MARIA OS
6 steps, full governance, evidence-backed
Same process. Structured governance. 93% faster.
AIが提案し、ゲートが決定する
すべての最適化候補は5つのゲートを通過しなければならない。例外なし。
Proposed Optimization
Auto-approve invoices under $5,000
Risk Tier
Responsibility
Evidence
Policy
Execution Safety
Gate Stack Result
Awaiting evaluation...
Every optimization MARIA proposes must pass through 5 safety gates.
リスクが上がると、人間が引き継ぐ
その比率は設定ではない。リスク、エビデンス、責任ゲートによって決定される。
Agent collects, organizes, detects gaps
“Gather all PO history and vendor data”
Agent evaluates within limits
“Auto-approve standard office supplies”
Agent proposes, human confirms
“New vendor onboarding — $10K contract”
Agent organizes evidence, human decides
“Terminate supplier relationship”
Agent stops and explains, human bears responsibility
“Major strategic acquisition”
As judgment weight increases, human share rises naturally.
The ratio is not a setting. It is determined by Risk, Evidence, and Responsibility Gates.
As Judgment Progresses,
Human Ratio Emerges
Decisions don't complete in an instant.
As evidence builds, human ratio naturally rises.
Responsibility Is Not Implicit.
It Is Confirmed with a Click.
HR = 0.30R + 0.25(1-E) + 0.25H + 0.10(1-V) + 0.10P
Human Ratio = 0.42
Contract Amount Change Approval
Risk Tier: Medium · Scope: 1 customer · Reversible
Responsibility is not yet assigned.
AI assists the judgment.
Humans accept the responsibility.
That moment is visible in the UI.
Even When AI Runs,
Responsibility Stays with the Human
Immutable · Non-deletable · Valid until execution ends
Task C paused — Unexpected input detected
Decision owner attention required. Responsibility anchor referenced.
AI runs the execution.
But responsibility never leaves the anchor.
Responsibility Has a Lifecycle.
It Shrinks, but Never Disappears Silently.
Approval
Execution
Completion
Validation
Archive
Responsibility closes on evidence, not on time.
Even after archive, responsibility can re-open for:
A new Responsibility Anchor is created. Past anchors are never reused.
Accept responsibility at decision.
Hold it through execution.
Close it on evidence.
MARIA OS designs the full lifecycle.
お問い合わせ
Workflow Scanner に関するお問い合わせ
目標、期限、制約条件、対象システムをお知らせください。スコープと実行ステップをご提示いたします。