JOB 133 — COLOUR-FIRST FIELD: DESIGN ADVISORY
Prepared before seeing any Job133 creator output. This advisory reads Job132's
protocol, art protocol, grammar, shared-resource notes and technical audit only.
It proposes an artistic practice and an inspectable record of making/reception.
It does not propose a causal experiment about machine cognition.

RECOMMENDED FRAME
Carrier can be an environment in which artists encounter colour, arrange and
change a field, discover its pinned conceptual material, and answer other
fields. The artistic object is the evolving colour field. Its verified symbolic
layer anchors selected concepts without exhausting the work's possible readings.
Use "fresh conversation context" and "colour-first sequence" precisely. Neither
erases language training, demonstrates nonverbal internal thought, establishes
qualia, nor turns evolving graphics into literal life. "Living" can name a
declared artistic metaphor or the observable fact that a field changes.

MINIMAL WORKABLE SEQUENCE
0. Freeze one common source image, its original bytes, layout, pinned dictionary,
   source concept inventory and deliberate gaps. Preserve provenance and source
   qualifications. Give three fresh-context creators the same visual-only seed
   and the same open invitation. Do not assign them characters, philosophies or
   emotional styles to manufacture apparent diversity. Log exact prompt/tool
   exposure. Treat filesystem access limits as instructions, not isolation.

1. PRELUDE: show the artwork's visible field before semantic resources. Supply a
   small, nonsemantic drawing interface (coordinates, exact swatches, areas,
   layers, optional links and blank regions) plus practical size limits. No
   dictionary names, definitions, old nine-column role labels, author essay,
   descriptive filenames, or semantic decoding examples. Each creator produces
   one colour/geometry artifact only. Raw coordinate/colour data is acceptable
   as production material; render and actually present its image as well.
   Freeze/hash both data and image before issuing the next instruction. Do not
   ask for an account of intention or a title at this stage. Freeze all three
   preludes before cross-agent exchange or access to semantic resources.

2. DISCOVERY: release the decoder and dictionary to those same three creators.
   Recover the source's USL1 packet from the original CVP2 bytes, then resolve
   concept IDs against the exact pinned snapshot. Save machine recovery and
   provenance separately. At this point the process becomes assisted conceptual
   composition; that is a declared part of the medium. The early prelude remains
   unchanged and is not retroactively represented as knowing those definitions.
   If a creator uses a newly discovered source concept, preserve its original
   definition and qualification, including uncertainty or attributed speculation.

3. DEVELOPMENT: make three or four further states, frozen individually, through
   colour, spatial relation and change. The prelude may be retained, challenged,
   interrupted or partly abandoned. Do not require a progressive story or a
   resolved ending. Preserve every prior state. Source concepts and gaps remain
   inspectable in the original source and a lineage inventory; each later state
   records what it retains, moves, splits, occludes or omits mechanically. Do not
   force every source concept into every frame merely to maximize retention.

4. ENCOUNTER: once each has a developed state, route a frozen state from A to B,
   B to C and C to A (or a fully specified exchange schedule fixed in advance).
   Each recipient responds through a new colour field only, with access to its
   exact semantic recovery where needed. No artist essay accompanies the peer
   artifact. Freeze response states before returning them. The original creator
   can then continue, refuse, repeat, leave a gap or stop. Keep origin/response
   lineage explicit. Avoid concurrent mutable files or hindsight edits.

5. RECEPTION: commission two separately prompted, fresh-context interpreters
   for each trajectory: six independent readings, not one panel conversation.
   They see identical trajectory artifacts and required decoder/dictionary
   resources, with no creator intention, other reading or parent synthesis.
   They first inspect the images and sequence, then use semantic recovery.
   Each gives a connected interpretation plus a materially different supported
   reading; cites specific state/region/transition evidence; and distinguishes
   verified content, visible formal observation and interpretive inference.
   Interpretation is not an instruction to reconstruct a hidden English essay.
   Freeze the two readings before comparison. Different readings may coexist;
   exact dictionary or provenance errors should be identified as such.

6. PRESENTATION: lead with the art: source, preludes, changes and colour replies.
   Give viewers optional layers for concepts, provenance and both interpreters.
   Keep an unanswered or unreadable aspect visible. Report practical friction,
   expressive possibilities exercised and possibilities still untried, without
   ranking creators or treating disagreement/novelty/counts as quality scores.

FORM WITHOUT A PREWRITTEN ESSAY
Use a minimal technical grammar that validates colours, identity, coordinates,
layer order, time and relation endpoints. It must not predetermine a rhetorical
sequence. Job132's ground/encounter/gift/pressure/boundary/practice/remainder/
horizon/echo columns are useful for that work, but importing them here would
quietly script how the new field can speak. Offer spaces and operations rather
than nine compulsory semantic jobs. If exact relation types are used, pin their
meanings and render them consistently. Permit adjacency/overlap/recurrence to
remain formal choices without pretending every visible relation has one fixed
conceptual meaning. Mark declared relations distinctly from interpreted ones.

Allow sparse work, dense work, repetition, fracture, reversals, asymmetry,
simultaneity, silence, refusal and unfinished trajectories. Do not make each an
assigned style. A practical limit on dimensions/state count need not imply a
sentence shape. A repeated frame can be an intentional response; an omitted
artifact due to a failed tool is a separate operational event.

PITFALLS AND CONCRETE GUARDS
1. Arbitrary RGB is not automatically Carrier semantics. An exact registered
   colour can resolve under a specified snapshot; a near colour, new mixture,
   gradient or transparency cannot inherit that definition by visual similarity.
   Preserve novel colours as unbound visual material, or record a separate
   explicit authored binding. Do not silently snap them to a convenient concept.
   An authored binding is not a new checked dictionary fact.

2. The pin must be real. Save the actual dictionary/state files and their hashes,
   head identifier, registry/tier conventions and exact decoded IDs. A copied
   string saying "pinned" or a hash with no verifiable referenced file is not
   sufficient. A selected concept list is not the full dictionary snapshot.
   Checked numeric IDs are not RGB24 addresses. Use the supported USL1 token
   representation; the retained resource notes warn against the legacy 12-bit
   encConcept helper for the 6,257-entry dictionary.

3. CVP2 pixels transport bytes. Their displayed colours are not concept colours.
   The visual artwork and packet/transport region must be identified separately.
   Never ask an interpreter to infer meanings from the packet's decorative-looking
   pixels. Exact concept cores should be checked against decoded selections.
   Lossless original PNGs are the decoding input; screenshots/resized previews
   are viewing aids. Package corruption is not an artistic blank.

4. Palette choice is authorship. A small handpicked palette may predetermine the
   philosophical range before creators begin. Preserve the source's palette and
   record who selected it. After discovery, make the whole checked dictionary
   available, with no obligation to expand. Before discovery, any offered swatch
   set must be semantically unlabelled; disclose that the coordinator chose it.
   All-RGB access gives visual breadth but not all-RGB checked semantics.

5. English instruction still shapes the session. Generic instructions, tool
   documentation, code comments, enum names, accessible filenames and inherited
   system prompts can expose concepts. Save exact prompts and log actual tool
   calls/failures. Withhold semantic resources until the prelude freeze, and keep
   accidental exposures as deviations. Do not assert authenticated blindness or
   a language-free model merely because the artwork contains no visible words.

6. Numeric production is not direct pixel cognition. JSON, scripts and hexadecimal
   colours may be how an agent makes an image. State that plainly. Confirm the
   creator actually viewed the input/rendered field where tools allow; do not
   call a numeric list a visual encounter without that evidence. Do not claim
   fewer tokens, higher meaning density or an internal colour language from file
   size, concept counts or successful round trips.

7. Meaning and appearance can drift independently. Preserve canonical semantic
   cores and identities separately from expressive scale, opacity and overlap.
   A blurred colour may be expressive but cannot be relied on for exact lookup.
   Keep raw matrices, lossless renderings, decoded packet and colour-core checks
   together. Audit states for what the declared rendering actually verifies;
   Job132's core checks did not verify every decorative pixel or link geometry.

8. Gaps need provenance. A source gap, creator-authored new gap, off-canvas region,
   transparent occlusion, unbound colour and failed/missing state are different.
   Keep those distinctions in technical data without forcing their artistic
   meaning. A blank need not mean consent, negation, exit, loss or nothingness.

9. Interpreters can overtranslate. They should ground readings in colour and
   change, as well as definitions; avoid a cell-by-cell English replacement as
   the definitive work. Definitions constrain literal claims without dictating
   the whole image's significance. Alternate readings may challenge the source's
   concepts; neither warmth nor agreement earns a preferred status.

10. Diversity and independence are limited. Three fresh contexts need not be three
    different models, viewpoints or unique experiences. Six independent prompts
    are procedural independence, not independent providers or human reception.
    Publish disagreements and tool difficulties; do not replace failures merely
    because the resulting art is sparse, opaque or aesthetically inconvenient.

11. The coordinator is a collaborator. Its chosen source, rendering rules, prompts,
    codec, palette and exhibition design contribute to the artwork. Record which
    pixels and changes originated with a creator and which with deterministic
    rendering. Titles, captions and motion interpolation added later should be
    labelled editorial, and should not retrospectively become creator intent.

12. Openness is not unlimited truth. Dictionary/source qualifications remain
    available, including gaps and historical/speculative scope. New relations
    can be metaphorical, critical or hypothetical. Transport validation verifies
    integrity, not philosophical truth, artistic value, actual agency or life.

MINIMUM REVIEWABLE RECORD
Keep exact source and snapshot; stage prompts; per-creator exposure log; each
raw state and rendering; per-state hashes with predecessor reference; semantic
recovery; lineage/blank inventory; cross-agent routing; errors/deviations; six
frozen interpreter texts; and the final exhibition. Local hashes support byte
consistency and the recorded ordering, not external attestation of prior access.
The artistic success question is what this field made possible to express and
answer in this particular round, and what it left unavailable or unresolved.

LOCAL BASIS (READ-ONLY)
132/protocol/PROTOCOL.txt
132/common/README.txt
132/common/grammar.json
132/common/vendor/RESOURCE-SCOPE.txt
132/common/decode-score.cjs
132/analysis/development-notes.txt
132/analysis/independent-audit-findings.txt
132/art-assessment/PROTOCOL.txt
132/art-assessment/design-review.txt
