Public-ready repository skill

Context Canvas surface reading

Reads a Context Canvas page or route family as a visitor surface and primary design input. Applies before assessment, planning, or material changes to a Canvas page, embedded instrument, or family relationship.

Source and version

Repository path
.agents/skills/context-canvas-surface-reading/SKILL.md
Source revision
341bceb719a28be760775b6322021d78abaa919b
Source SHA-256
b0861479adc855a26c4c2d7a62d49a436f44a803e3c28a406da28c26b83d7188
Publication standing
Public ready

Included source files

This skill has no additional files in its public source package.

Complete skill source

The Markdown below matches the exact source text. The format link above opens the file on its own.

---
name: context-canvas-surface-reading
description: Reads a Context Canvas page or route family as a visitor surface and primary design input. Applies before assessment, planning, or material changes to a Canvas page, embedded instrument, or family relationship.
---

# Context Canvas surface reading

## Contract

- **What:** A source-grounded model of one page or route family.
- **When:** Assessment, planning, or material visitor-surface change begins.
- **Boundaries:** Page meaning remains rooted in authored source, evidence boundaries, and human authority. Visual variation remains available within the wider grammar.
- **Result:** Route standing, visitor ability, evidence boundary, runtime owners, visual fingerprint, and affected family.

## Rules

### Rule: The page is design input

Prose, diagrams, composition, and interaction patterns can shape later repository work. Page content is therefore read as behavior and design evidence rather than interchangeable copy.

### Rule: Contracts orient; routes compose

Visual Fidelity Contracts stabilize semantic grammar and canonical references. Route families retain authority over palette, rhythm, density, spatial arrangement, delivery mechanism, and source-earned experiments.

### Rule: Runtime ownership stays explicit

HTML owns meaning and reading order. CSS owns presentation and modes. Progressive JavaScript owns bounded enhancement. Embedded systems and delivery boundaries retain separate authority.

### Rule: Reading depth follows decision leverage

A catalog or full-family question begins with aggregate route, class, asset, iframe, stylesheet, and runtime inventory. Complete source reading then deepens around exceptions, affected consumers, and relationships capable of changing the decision. A material change to one page still receives its complete shaping source.

### Rule: Semantic and rendered observations stay reconcilable

Document meaning, accessibility-tree or DOM representation, rendered visibility, geometry, and screenshot content are distinct observation channels. Agreement in one channel leaves the others open. When an AI-visitor claim enters, the reading identifies the agent's actual channel and version, compares it with the corresponding human-visible task, and treats benchmark architecture as a hypothesis source until a local task supplies behavior evidence.

## Operating sequence

1. **Orientation:** The reading begins at `context-canvas-project-surface/context-canvas/README.md`.
2. **Complete source:** One target page receives each materially shaping stylesheet, script, iframe, SVG, image, manifest, and data source. Catalog-scale work uses inventory to locate the exceptions and affected consumers that receive this depth.
3. **Grammar:** The relevant record under `visual-fidelity-contracts/` and one canonical sibling supply family relationships when those relationships matter.
4. **Delivery context:** `context-canvas-project-surface/context-canvas/grammar-family.html` supplies repository context when Cloudflare, contextual composition, coordinated rooms, durable undertakings, or visitor-owned surfaces enter the question.
5. **Surface map:** The reading records standing, visitor ability, evidence boundary, composition fingerprint, runtime owners, and family relationships.
6. **Consequence map:** The resulting map names the improved visitor ability, source owner, affected family, smallest useful observation, and human-held decision authority.

## Representative scenarios

### Scenario: A composed Debrief receives a visual change

- Given a Debrief carries shared composition grammar and a route-specific fingerprint
- When a visual change is assessed
- Then shared contract relationships and route-local expression are mapped separately
- And the comparison preserves meaningful variation while surfacing material regression

### Scenario: A Cloudflare reference appears inside a page

- Given a page includes a Cloudflare mechanism or contextual-delivery concept
- When the page's implementation implications are assessed
- Then `grammar-family.html` supplies repository context
- And current official Cloudflare documentation supplies contemporary platform facts

## Completion

Surface reading completes when the page can be explained through standing, visitor ability, evidence, ownership, fingerprint, and family relationships rather than title alone.