Trigger
Marketplace rules, tax treatment, logistics requirements, product procedures or role SOPs change, or an operator requests source-backed knowledge while performing a task.
SCENARIO-DETAIL / LOCALIZED DECISION BRIEF
Business trigger: Marketplace rules, tax treatment, logistics requirements, product procedures or role SOPs change, or an operator requests source-backed knowledge while performing a task.
REFERENCE_ARCHITECTURE · GOVERNED_WRITE

DECISION RECORD / C.09
Source-traceable reference · pp.22–23
Marketplace rules, tax treatment, logistics requirements, product procedures or role SOPs change, or an operator requests source-backed knowledge while performing a task.
Turn planning, procurement, logistics, operations, content, service, finance and compliance material into sourced, versioned role knowledge callable by an Agent.
When sources are stale, evidence conflicts or access is insufficient, return review required or unavailable. Never treat model memory as a formal rule, and never place sensitive files in an unauthorized index.
Every knowledge fragment resolves to a source; role boundaries are clear; publication is versioned and reviewed; each invocation is traceable; expiry and conflicts have a maintenance loop.
Choose one role and a set of formal sources, then define publication review, expiry and unauthorized-query boundaries.
KNOWLEDGE → COMPARISON → DIRECTION → OPTIMIZATION
The full-detail canonical evidence record remains available in Chinese. IDs, Truth classes, boundaries, and source references stay unchanged across languages.
Source-traceable reference
Compare the same operating fields before choosing a direction.
Confirm the owner, authority, human gate, and readback rule.
Define a baseline, target, owner, and observation window before claiming impact.