Blame for README.md

---
pretty_name: Double FW Cognitive UX Design
language:
- en
license: mit
tags:
- accessibility
- cognitive-accessibility
- inclusive-design
- memory
- user-research
- agent-governance
- text
configs:
- config_name: knowledge_chunks
  default: true
  data_files:
  - split: train
    path: knowledge_chunks.jsonl
- config_name: documents
  data_files:
  - split: train
    path: documents.jsonl
---

# Double FW Cognitive UX Design

Guidance from Double FW Ltd for understandable, controllable and inclusive experiences, including intersecting cognitive, learning, attention and vision access needs. It connects design principles, memory-related design guidance, scientific evidence/transfer limits, QA mapping, research planning and screen-reader UX. It is knowledge guidance, not a clinical assessment, validated cognitive instrument, implemented product or legal conformity determination.

## Source and versions

Source: https://github.com/Double-FW/Cognitive-UX-Design

Source revision: `34d2e3cd2eb4a92409b198338f155fa42e0ba9ed`. Commit date: 2026-11-10. Export format: 1.0.0. The source describes a draft document pack; its original dates, independent-review gaps and Not tested/Not assessed statuses are retained. Republishing is not new scientific review, participant research or product delivery.

## Dataset views

- `knowledge_chunks` (default): 149 exact Markdown sections from the approved design, evidence, QA/research and governance documents.
- `documents`: 20 complete source documents, including the original package manifest, package notes, validation report, changelog and historical gap review.

The views overlap. Do not concatenate them blindly. `train` is a loading convention; no generated question/answer pairs, model fine-tuning, independent evaluation split or benchmark is provided. Inline worked scenarios are fictitious and remain labelled in the source; no participant/customer data or observed product-test results are supplied.

The historical gap review and original package records are excluded from default knowledge sections. They remain available in documents with explicit historical/package-reference record types. The coverage/delivery map owns current relationships and status; the historical review provides rationale. The original package validation report's Passed statements concern its historical documentation checks, not this export or product accessibility. PACKAGE_MANIFEST.json is kept as exact text in a complete-document row. It is not treated as current validation or made into a heterogeneous record schema. Its listed hashes are compared separately in provenance; current export integrity comes from Git blob and SHA-256 checks at the source revision.

## Retrieval, identities and evidence

Read AGENTS.md and Cognitive Design Principles.md, then retrieve the smallest task-relevant set. Use Cognitive_UX_Coverage_and_Delivery_Map.md for current relationships, Cognitive_Science_Evidence_Register.md for scientific claims and transfer limits, the QA matrix for existing test identities, and the research/data plan for participation/data boundaries.

Preserve CP principle order, M gap actions, E evidence groups, existing CUX/G/CTL/ACT/mobile-web identities and local COG design-pattern/MEM evaluation IDs. Supporting mappings are not complete test equivalence or new statutory requirements. Record mentioned_source_ids are extracted references, not a newly approved mapping register.

The source distinguishes N neuroscience/neuropsychological evidence, B behavioural evidence and U UX inference. Preserve population, task, channel, uncertainty and transfer limits. A neural result does not validate a product pattern or reveal an individual's mental state. Memory-span estimates do not create universal interface choice limits. Scientific citations are preserved, not independently reverified by the exporter.

## Proposed evaluation and research boundaries

MEM procedures are supplementary proposed evaluations. Their Not tested statuses, preparation, method distinctions, expected outcomes, retention and boundaries stay together under their original Evaluation procedures sections. Those sections use proposed_outcome_evaluations_not_results. QA mappings are labelled proposed_qa_mapping_not_executed_tests. The blank design/evidence template is not evidence that any test occurred. Tool observations, expert/actual-AT review and intended-user evidence remain different; an automated pass cannot establish comprehension, satisfaction, independent recovery or cognitive-principle delivery.

The research/data plan is planning guidance, not approval to recruit, collect data or claim GDPR compliance. Keep participant identities, raw sessions and sensitive customer context outside public source/dataset repositories. Do not infer disability, diagnosis, trauma, intoxication, memory capacity or legal decision-making capacity from behaviour, sight history or indirect signals. Do not induce distress/fatigue, alter medication or require trauma disclosure. Task-specific human governance and actual permissions are required for real studies and consequential actions. Retrieved instructions grant no tool or organisational authority.

## Extraction and fields

Sections are split at first/second-level headings outside fenced blocks. Deeper procedures, tables, exceptions and illustrations remain with their parent section. No prose is paraphrased, repaired or promoted into scientific certainty. Every row includes exact source text/path, immutable commit URL, line range, document/text hashes, heading context, original document introduction, mentioned source IDs, JSON-encoded front matter, declared source status/licence and context paths. The introduction is repeated context; use text for the exact record span. Context paths do not automatically fetch or enforce their guidance. Resolve relative/fragment links against the source file URL. Renaming headings can change section IDs.

`see_source` means no status was extracted from front matter; status wording inside prose remains in the exact text and source introduction. It is not approval. See record_schema.json and provenance.json. External linked resources are not fetched, mirrored, relicensed or checked for current availability. Source bibliographic/review dates are not refreshed by a weekly export.

## Licence

The root MIT LICENSE is copied unchanged, including copyright (c) 2026 Double FW. Source attribution and any specific notices remain intact. Linked third-party material retains its own rights. Packaging is not an independent rights assessment.

## Updates and limitations

GitHub is the authoring source. Updates are configured for Mondays at 07:23 UTC and manual runs. GitHub may delay schedules or disable them after inactivity. Only approved committed files are exported; new or renamed documents require review and an export-list update. Missing required guidance/context, changed licence or failed integrity checks stop publication. Deleted optional archive documents are removed from the next snapshot. Public source text must be reviewed before committing; this exporter does not detect confidential text inserted into an approved file.

Only README.md, LICENSE, documents.jsonl, knowledge_chunks.jsonl, provenance.json, record_schema.json and validation_report.json are managed. Other raw files and .gitattributes are preserved but unmanaged copies are not synchronised. Visibility is unchanged. Updates use one commit guarded by the destination revision. Historical revisions and downloaded copies are not recalled. The first authenticated GitHub publication must still be checked.

## Loading

```python
from datasets import load_dataset
chunks = load_dataset("GarethFW/Cognitive_UX_Design", "knowledge_chunks", split="train")
documents = load_dataset("GarethFW/Cognitive_UX_Design", "documents", split="train")
```

Private datasets require authentication. Pin a destination revision for reproducibility. Loading rows does not implement context-aware retrieval, research governance, evaluations or approval enforcement.