Preference facts

2 min readReferenceUpdated 2026-05-19

What you'll find here

The PreferenceFact record — how Craik models user and team preferences as reviewable records, never as silently-approved facts.

Inferred preferences are not approved.

Inferred preferences must cite evidence, receipts, and inferred-from references, and they must not include review fields.

Fields

Preference id

Subject

E.g. user:maintainer · team:platform.

Scope

user or team.

Preference statement

Status

inferred · approved · rejected.

Confidence

Evidence ids

Receipt ids

Inferred-from references

Optional review fields

Creation timestamp

Review fields required for decided records.

Approved and rejected preferences require reviewer, reason, and review timestamp.

Scope boundary

Scope

Subject prefix

Promotion rule

User preference

user:

Stays user-scoped.

Team preference

team:

Do not promote a user preference to team scope without an explicit review decision and evidence for the broader scope.

What's next

ReferenceMemory review nudgesThe reminder layer that surfaces stale preferences for review.ReferenceLearning receiptsThe receipt subtype for preference reviews.GuideLearning loopsThe full discipline preference review sits inside.