Tag: review systems
-
Field Note 055: Decision Half-Life
Decision half-life measures how quickly a conclusion loses reliability as its evidence, environment, and operating assumptions change.
-
Operator Brief: Signal Recovery
A practical operator brief for signal recovery: restoring clarity after noise, stale routes, moderation cleanup, or interrupted publishing cycles.
-
Operator Brief: Continuity Check
A practical operator brief for continuity checks: confirming that content, forum prompts, chat posture, and search surfaces still point in the same direction.
-
Operator Brief: Route Receipt
A practical operator brief for route receipts: recording when a path was checked, what it returned, and what should happen next.
-
Operator Brief: Evidence Gradient
A practical operator brief for using evidence gradients to separate strong signals, weak hints, stale claims, and action-ready findings.
-
Field Note 041: Source Expiry
A field note on source expiry: deciding when old links, stale references, and aging evidence need review before they keep shaping the site.
-
Field Note 040: Audit Marker
A field note on audit markers: small, repeatable signals that show when a review happened, what changed, and what still needs watching.
-
Operator Brief: Escalation Threshold
A practical operator brief for escalation thresholds: deciding when a recurring signal, account, file, or moderation issue needs a stronger response.
-
Field Note 039: Route Evidence
A field note on route evidence: using logs, links, referrals, and member behavior to prove which paths are actually carrying the site.
-
Intel Report 036: Signal Debt
Intel Report 036 defines signal debt: the backlog created when unresolved alerts, prompts, chat volume, and review notes keep asking for attention.