Patterns and learning source context
This reference preserves cross-cutting context for observed patterns and their relationship to signals, proposals, profile knowledge, and History. It does not create requirements independently; binding statements are repeated in the applicable CRDs.
Source roles and limits
| Source | Role | Can establish | Cannot establish alone |
|---|---|---|---|
| Current PIOS framework | architecture authority | epistemic separation among events, observed patterns, proposed Meaning, confirmed Meaning, and Learning | one detection algorithm, universal threshold, or realization availability |
| Historical PIOS Global at the selected revision | historical design evidence | evidence thresholds, lifecycle states, proposal gating, temporal refresh, and user-facing pattern intent | current architecture authority or current implementation |
Restricted application evidence RAS-01 | requirements and potential realization evidence | application-specific pattern requirements, declared structures, and traced implementation evidence where present | public disclosure, tested behavior, deployment, or production availability without separate evidence |
Cross-cutting context
- Signals and source events are evidence inputs; they are not observed patterns by themselves.
- Observed patterns describe recurrence and remain non-authoritative even when stable.
- Pattern detection and later lifecycle evaluation are separate outcomes: one creates an evidence-backed emerging pattern, while the other reassesses strength, status, and eligibility over time.
- Proposal eligibility is not proposal creation, and a proposal is not a confirmed profile assertion.
- Pattern summaries and inspection screens are projections over pattern and evidence state rather than separate sources of truth.
- Source bias, coverage gaps, time windows, and evidence decay remain visible because frequency is not importance and recurrence is not preference.
Evidence maturity
Current and historical sources support the reusable pattern definitions. Restricted sources contain requirements and declared pattern structures, while the inspected application surfaces describe disabled or planned behavior rather than confirming an active detection or refresh realization. Tests, deployment, and production behavior remain unknown.
Sequencing context
This tranche covers observed-pattern detection and lifecycle evaluation. Signal extraction, proposal decision, profile assertion, History compilation, and owner-facing inspection remain separate capabilities or projections.