REGISTRY_AUDITeps_protocol
Provision Node
Logic Specification: T3

EPS Protocol.

Execution Probability Scoring: The standardized mathematical metric for objective project health.

Operational Goal

The EPS Protocol was designed to eliminate "Optimism Bias" in project management. In traditional systems, "In Progress" is a binary state. In 2asana, every active node carries a probability score from 0 to 100, representing its likelihood of on-time completion based on established narrative and temporal signals.

Identity-Aware Calibration (RACI)

V2.0 of the protocol introduces **RACI-Aware Scoring**. The engine no longer treats all silence as risk. It calibrates deductions based on the assignee's engagement tier:

Active Drivers
Primary executors are subject to full "Linguistic Staleness" penalties. If a Driver is silent for >7 days, the node's EPS decays rapidly, signaling a critical lack of tactical momentum.
Informed Observers
Observers are added for visibility. The engine **heavily reduces** staleness penalties for these members, ensuring that their passive involvement does not create false-positive risk alerts in the registry.

The 4 Authority Vectors

Narrative Sentiment

AI analyzes the comment history for "friction clusters." Mention of "blockers," "waiting," or frustrating tonal markers results in immediate score deduction.

Temporal Delta

Measures the proximity to the deadline relative to activity acceleration. Scores decay automatically if a node shows zero narrative movement.

Governance Rules

User-defined **Project Rules** can apply mandatory multipliers. A "Strict" rule can force a score to 0 if specific filters are met.

Structural Weight

Tasks linked to multiple downstream dependencies or "High-Leverage" Strategic Verticals are prioritized for deep analysis.

Signal Treatment Matrix

The inference engine starts every active node at a base of 100 EPS. Deductions are then applied based on discovered signals in the tactical registry.

-10 EPS

Negative Sentiment

Detected frustration, repetitive blockers, or aggressive tonal markers in task stories.

-15 EPS

Execution Stale (7d)

The task has remained in the same state with zero narrative activity for more than 7 solar days.

-10 EPS

Deadline Proximity

Task is due in less than 72 hours and has not moved to a 'Review' or 'Verification' stage.

-20 EPS

Active Blocker

Explicit mention of 'blocked,' 'stuck,' or 'waiting' in recent comments without a resolution follow-up.

-25 EPS

Deadline Breach

The node is past its due date boundary and is not marked as completed in the registry.

-5 EPS

Identity Failure

Node is active in the registry but is missing a primary owner (unassigned) or strategic vertical mapping.

Risk Stratification

80 - 100

Low Risk: Strategic Driver

Activity is consistent, sentiment is positive/neutral, and the deadline is respected.

50 - 79

Medium Risk: At Risk

Minor friction detected or activity is starting to plateau relative to the deadline window.

0 - 49

High Risk: Critical Breach

Significant blockers identified or node is past due with zero recovery activity.

Automation Loop

EPS scores are not static. The **Master Hourly Worker** triggers a recalculation pass whenever new narrative pulses are ingested, ensuring that the **Daily Brief** always reflects the most recent probability of success.

View Active Registry