SI001 – Session Consistency
Overview
Assessment for session consistency and domain concurrency tracking. Uses context.metadata to ensure one analysis session per domain and consistent session data/timing.
Probability that AI systems use this signal: Crawlers and generative AI pipelines consume structured and visible page signals for training and inference. Assessment-specific signals (e.g. schema, canonicals, trust cues) affect how likely a page is indexed and surfaced. The probability that this assessment's signal influences AI behavior is high when the page is in a product or compliance context.
Impact on geo compliance: Passing this assessment supports geo compliance by ensuring machine-readable and visible content meet standards that reduce the risk of wrong locale, pricing, or trust in AI-generated answers. Failing can lead to non-compliant or misleading surfacing.
What We Check
- **context.metadata** required. Keys: domain_concurrency (bool), session_data_consistent (bool), session_start_time (ISO), session_duration_ms.
- **domain_concurrency true:** −50 (another session active for domain).
- **session_data_consistent false:** −50.
- **session_start_time:** parsed as ISO; if older than 1 hour: −20; invalid format: −10.
- **session_duration_ms > 300000 (5 min):** −15.
Pass / Fail and Score
- **PASSED** if score >= 60. Details: analysis_session_id, domain, concurrency, data consistent.
How to Fix When It Fails
- Ensure only one analysis session per domain at a time; verify session data integrity; refresh long-lived sessions; use ISO timestamps.
Common Issues
- Concurrent sessions for same domain; inconsistent session data; very old or long sessions.
Dependencies
None. SD006 (Dynamic Data Stability) depends on SI001.
How to Verify
- Check metadata population and session lifecycle; avoid duplicate concurrent runs per domain.
Additional Resources
- Session design; idempotency; concurrency control