KAIA WORKSHOP
CARRIER PIGEON TRANSPORT RULE
LONG INSTRUCTION DELIVERY STANDARD
Purpose:
Long instructions must be transported safely without changing,
compressing, or weakening their technical content.
This rule concerns TRANSPORT only.
It does not change product specifications, authority, construction scope,
or specialist responsibilities.
==================================================
1. CORE PRINCIPLE
==================================================
WRITE THE COMPLETE INSTRUCTION FIRST.
Do not design an instruction around the amount that fits in one message.
First determine the complete instruction required for safe execution,
including all:
– scope
– authority
– boundaries
– prohibitions
– STOP conditions
– evidence requirements
– inspection requirements
– return/report requirements
Only AFTER the complete instruction is conceptually finished should it
be divided for transport.
The transport must fit the specification.
The specification must NOT be reduced to fit the transport.
WORKSHOP RULE:
仕様書に鳩を合わせる。
鳩に仕様書を合わせない★
==================================================
2. PIGEON COUNT IS NOT FIXED
==================================================
There is no preferred or maximum number of carrier pigeons.
Use as many PARTS as required.
If the complete instruction safely fits in:
3 parts → use 3.
5 parts → use 5.
8 parts → use 8.
12 parts → use 12.
Never compress, omit, merge, or weaken important material merely to
meet an arbitrary PART count.
WORKSHOP RULE:
長いなら削るな。
仲間を呼べ★
==================================================
3. PRACTICAL TRANSPORT SIZE
==================================================
For Shamyue physical copy/carry transport, use approximately:
3,000–4,000 characters per PART
as a practical cruising range.
This is a TRANSPORT HEURISTIC,
not a hard technical limit.
Around:
3,500 characters
is a useful normal target.
If a PART naturally approaches or exceeds approximately:
4,000 characters
prefer another carrier pigeon when there is a clean semantic split.
Do NOT deliberately fill a PART up to 5,000 characters merely because
it might technically fit.
If uncertain:
USE ANOTHER PART.
==================================================
4. SEMANTIC SPLITTING
==================================================
Split at meaningful section boundaries.
Good split points include:
– package identity
– authority decisions
– architecture
– state semantics
– addressing
– persistence rules
– prohibited machinery
– STOP gates
– construction authorization
– static inspection
– success return requirements
Do NOT split:
– in the middle of a sentence
– in the middle of one safety rule
– where the next PART could reverse the apparent meaning of the
previous PART
– merely to hit an exact character count
Transport size is secondary to semantic integrity.
==================================================
5. PART NUMBERING
==================================================
Every multipart instruction must clearly identify:
PART X OF N
Example:
PART 1 OF 5
PART 2 OF 5
PART 3 OF 5
PART 4 OF 5
PART 5 OF 5
All PARTS together constitute ONE instruction.
Individual PARTS are not independent instructions unless explicitly
stated otherwise.
==================================================
6. EXECUTION GATE
==================================================
When execution must wait until the complete instruction arrives, say so
explicitly.
Intermediate PARTS should contain an instruction equivalent to:
DO NOT EXECUTE UNTIL ALL PARTS ARE RECEIVED.
The final PART should require verification that every PART was received
completely.
Only after complete receipt may the final PART state:
COMPLETE SET → GO
If any PART is missing or incomplete:
STOP.
Request the missing PART.
DO NOT CONSTRUCT.
==================================================
7. NO INTERPRETATION BY THE CARRIER
==================================================
Shamyue may physically carry text between threads, specialists, devices,
or workspaces.
The carrier is not responsible for reconciling technical meaning.
Therefore instructions must be self-routing and sufficiently explicit
for the receiving specialist.
WORKSHOP RULE:
🕊️ DOES NOT INTERPRET.
Do not rely on Shamyue to:
– merge contradictory instructions
– infer missing sections
– explain architectural intent
– decide which version is authoritative
– repair an incomplete transport set
==================================================
8. WITHDRAWAL / SUPERSESSION
==================================================
If a previously delivered PART must be replaced:
FIRST send a small explicit withdrawal/correction message.
The withdrawal must identify exactly what is withdrawn.
Example:
PREVIOUS PART 1 OF 2 — WITHDRAWN
It must clearly state:
– the old PART is no longer valid
– it must not be used for execution
– it must not be combined with the replacement set
– construction remains paused until the replacement set is complete
Then issue a newly numbered coherent replacement set.
Do NOT silently replace a PART.
Do NOT leave the specialist to determine which overlapping instruction
is authoritative.
==================================================
9. DO NOT RESTRUCTURE A VALID DELIVERY WITHOUT EVIDENCE
==================================================
Transport success or failure is determined by Shamyue’s actual delivery
report.
Do NOT infer transport failure merely from:
– emoji
– tone
– a short reaction
– apparent message size
– assistant speculation
In particular:
🕊️💦
does NOT automatically mean:
TRANSPORT FAILED.
If Shamyue reports that the PART was delivered successfully:
treat it as delivered and valid unless another explicit correction is
made.
Do NOT withdraw, renumber, or restructure already valid PARTS merely
because the assistant becomes worried after delivery.
==================================================
10. CONTENT MUST NOT BE SACRIFICED
==================================================
Multipart transport must never remove important content merely to make
the PARTS smaller.
Do NOT sacrifice:
– safety boundaries
– STOP rules
– product ownership boundaries
– authority distinctions
– known WATCH conditions
– prohibited actions
– static inspection requirements
– evidence requirements
– return/report requirements
If all required material makes the instruction long:
ADD PIGEONS.
==================================================
11. MINIMIZE DUPLICATION
==================================================
Some repeated transport guards are useful, especially:
– PART X OF N
– withdrawn-set warning
– do-not-execute-yet warning
– missing-PART STOP rule
However, do not duplicate entire architectural sections across PARTS.
Each substantive section should normally have one authoritative home
inside the complete set.
This keeps every pigeon light without weakening the instruction.
==================================================
12. FINAL TRANSPORT CHECK
==================================================
Before sending a multipart instruction, check:
[ ] Complete instruction was determined before transport splitting. [ ] No specification was removed merely to reduce PART count. [ ] PART count follows content size rather than controlling it. [ ] Each PART is comfortably transportable. [ ] Approximately 3,000–4,000 characters is used as a practical target,not a hard limit.
[ ] Splits occur at semantic boundaries. [ ] Every PART has PART X OF N. [ ] Execution gate is explicit where required. [ ] Missing-PART behavior is explicit. [ ] Superseded material is explicitly withdrawn. [ ] Shamyue is not required to interpret technical meaning. [ ] Already successful transport is not invalidated by assistantspeculation.
[ ] Final PART clearly declares when the complete set may execute.==================================================
CANONICAL WORKSHOP SUMMARY
==================================================
FIRST:
Make the complete safe instruction.
SECOND:
Split it into comfortably transportable semantic sections.
THIRD:
Call as many pigeons as necessary.
NEVER:
Compress the specification to save pigeons.
☕🪑「長いな」
🕊️「削ります？」
☕🪑「いや、仲間呼べ★」
仕様書に鳩を合わせる。
鳩に仕様書を合わせない。
🕊️ DOES NOT INTERPRET.
No comments yet.