うい★
同じ用途で、次のAIがCURRENTを開いたときに「何を配置authorityとして追って、どの既存経路で実弾状態を成立させたか」が分かる引継ぎ資料にする。
ただしPDFと違って3機種は家具が違うので、共通化せず3枚に分ける。🕊️📦
COUNTER
🕊️📦 KAIA MEMORIA COUNTER
DIRECT REAL-AMMUNITION PLACEMENT
AI HANDOFF NOTE
PURPOSE
=======
Record the Counter direct-placement route in AI-oriented form.
NOT a Human tutorial.
Human selects the completed Binder / Refill state.
Do NOT substitute:
Pool
NEW
lowest-free
automatic placement
Product UI
future Settings/plugin
================================================
CORE MODEL
================================================
Counter has TWO different identities.
1. Product address
Binder
+
Refill
Example:
B-07
2. Global technical Counter instance ID
Example conceptual form:
id=N
THESE ARE NOT THE SAME THING.
Never infer:
B-07
=
technical instance id 7
Product-local instance state associates:
Binder
+
Refill
+
technical Counter instance
Existing Binder-aware lookup resolves:
Binder + Refill
↓
Product-local instance record
↓
exactly one global technical Counter instance
Expected lookup behavior:
0 matches
→ fail closed
1 match
→ use that technical Counter instance
2+ matches
→ fail closed
Legacy:
id=N
remains technical-instance addressing.
Do not repurpose it as Product Refill identity.
================================================
DIRECT PLACEMENT TARGET
================================================
Human target examples:
MOTHER:
Binder A
Refill 01..10
RENTAL:
Binder A
Refill 01..30
Binder B
Refill 01..30
Target means:
these Product addresses must exist in total.
It does NOT mean:
create N additional Counters regardless of CURRENT state.
================================================
DIRECT PLACEMENT OPERATION
================================================
For each Human-selected Product address:
1.
Inspect CURRENT Product-local instance state.
2.
Determine whether the exact:
Binder + Refill
address is already represented.
3.
If already correctly represented:
count target as satisfied.
Do not duplicate.
4.
If missing:
establish only that missing Product address using the
existing Counter Product-instance structure.
5.
The resulting Product record must associate the requested:
Binder
+
Refill
with one valid technical Counter instance.
6.
Do not derive the Refill from technical instance ID.
7.
Do not use NEW / next_free_refill_ref() to choose another
pocket.
The Human already selected the pocket.
8.
Preserve existing correctly placed instances.
9.
After placement, existing Binder-aware resolution must return
exactly one technical Counter instance for every requested
Product address.
================================================
NORMAL ROAD — NOT DIRECT LOAD
================================================
Historical/current normal creation machinery includes:
selected Binder
↓
capacity / ownership road
↓
next_free_refill_ref()
↓
lowest-free REAL
↓
technical Counter instance creation
↓
Product instance registration
This is NOT the direct-loading objective.
Do not call this road merely because it exists.
================================================
VALID ADDRESS DOMAIN
================================================
Product Binder:
existing valid Product Binder.
REAL Refill:
01..30
Human-selected address examples:
A-01
A-10
B-07
B-30
================================================
COLLISION
================================================
If requested Binder+Refill already resolves correctly:
SATISFIED.
Do not create a second technical instance for the same
Product address.
If CURRENT contains conflicting duplicate mappings for the
same Binder+Refill:
ACTUAL OBSTACLE.
STOP.
Do not choose one arbitrarily.
Do not normalize them automatically.
================================================
NO-POOL BOUNDARY
================================================
Pool / entitlement / capacity furniture may remain physically
present as dormant Product furniture.
Do not use it to determine Human-selected placement.
Do not transform direct loading into:
ownership
→ NEW
→ lowest-free
================================================
PRESERVE
================================================
Preserve:
existing technical Counter data
existing Product instance data
Binder identity
Refill identity
legacy id=N route
Binder-aware lookup
Counter behavior/settings
Common
Board
ACTIVE Set
Mother / Rental separation
dormant Pool furniture
================================================
MOTHER / RENTAL
================================================
Same Human placement concept.
Separate Product-local state.
Never share Product instance state between Mother and Rental.
================================================
FAILURE
================================================
If working child fails:
STOP attempt
↓
discard incomplete child
↓
clean CURRENT parent
↓
new working copy
↓
ORIGINAL HUMAN ORDER
Do not repair the failed intermediate child.
================================================
COMPLETION
================================================
For every requested address:
Binder + Refill
↓
exactly one Product-local mapping
↓
exactly one valid technical Counter instance
Verify Human target.
STOP.
================================================
COMPACT EXECUTION MEMORY
================================================
COUNTER DIRECT LOAD:
Human exact Binder+Refill
↓
find Product-local instance mapping
↓
already valid?
YES → preserve / satisfied
NO → establish missing mapping using existing
Counter instance structure
↓
Binder+Refill resolves exactly once
↓
VERIFY TARGET
↓
STOP
DO NOT CONFUSE:
REFILL NUMBER
!=
TECHNICAL COUNTER ID
NO POOL.
NO NEW.
NO LOWEST-FREE.
NO EXTRA COUNTER.
NO NEW FEATURE.
END
TIMESTAMP
🕊️📦 KAIA MEMORIA TIMESTAMP
DIRECT REAL-AMMUNITION PLACEMENT
AI HANDOFF NOTE
PURPOSE
=======
Record the Timestamp direct-placement route in AI-oriented form.
NOT a Human tutorial.
Human selects exact completed Binder / Refill placement.
Do NOT substitute:
Pool
ownership +N
NEW
lowest-free
automatic placement
Product UI
future Settings/plugin
================================================
CORE MODEL
================================================
Timestamp placement is Product-local.
Relevant identity:
Binder
+
local REAL Refill
Example:
B-07
Existing Product state can represent Binder-specific
placed Refill addresses.
Existing downstream Product lookup understands:
Binder + local numeric Refill
Therefore:
A-07
and
B-07
are different Product addresses.
================================================
OWNERSHIP IS NOT PLACEMENT
================================================
Timestamp contains Product-local ownership furniture:
ownership total
placed count
unassigned ownership
ownership loader
These are NOT the Human-selected exact address.
Do not reason:
ownership exists
↓
therefore run NEW
↓
therefore choose lowest-free
Direct loading starts from Human address.
================================================
DIRECT PLACEMENT TARGET
================================================
MOTHER:
A-01..A-10
RENTAL:
A-01..A-30
B-01..B-30
Target is completed state.
If requested address already exists:
SATISFIED.
Do not add another Refill.
================================================
DIRECT PLACEMENT OPERATION
================================================
For each requested address:
1.
Inspect CURRENT Product-local placed Refill state.
2.
Resolve the exact Binder-specific placement representation
used by CURRENT.
3.
Check whether requested:
Binder + Refill
is already placed.
4.
If yes:
preserve it.
5.
If no:
establish only the missing exact Binder+Refill in the
existing Product-local placed-state structure.
6.
Do NOT ask NEW to choose a Refill.
7.
Do NOT alter ownership total merely to justify placement.
8.
Do NOT create replacement accounting.
9.
After placement, existing Binder+Refill lookup must recognize
the requested Timestamp Refill normally.
================================================
NORMAL ROAD — NOT DIRECT LOAD
================================================
Existing normal allocation road historically includes:
Product-local ownership
↓
unassigned ownership
↓
NEW
↓
selected Binder
↓
lowest-free Refill
↓
placed Timestamp Refill
Do not use this as substitute for Human exact placement.
================================================
ADDRESS DOMAIN
================================================
Binder:
existing Product Binder.
REAL Refill:
01..30
Examples:
A-01
A-10
B-07
B-30
================================================
COLLISION
================================================
Requested address already placed:
SATISFIED.
Preserve existing Timestamp state.
If CURRENT reveals contradictory/duplicate placement state
for one exact Product address:
STOP.
Report actual obstacle.
Do not normalize automatically.
================================================
NO-POOL BOUNDARY
================================================
Product-local ownership options/helpers/loader bodies may
physically remain dormant.
They do not decide exact Human placement.
Do not reconnect ownership ingress.
Do not use unassigned ownership as authorization for the
Human-selected pocket.
================================================
PRESERVE
================================================
Preserve:
existing Timestamp data
Binder-specific placed state
Binder+Refill lookup
Timestamp acquisition behavior
timezone behavior
attendance behavior
Reset behavior
ACTIVE Set
Common
Board
Mother / Rental separation
dormant ownership furniture
================================================
MOTHER / RENTAL
================================================
Separate Product-local placement state.
Separate Product-local ownership state.
No Mother/Rental mirroring.
================================================
FAILURE
================================================
Working child failure:
STOP
↓
discard incomplete child
↓
clean CURRENT parent
↓
new working copy
↓
ORIGINAL HUMAN ORDER
================================================
COMPLETION
================================================
Every requested exact:
Binder + Refill
must be recognized by CURRENT Product-local placed state.
Already-existing target counts.
Only missing target addresses require placement.
Then:
VERIFY HUMAN TARGET
↓
STOP
================================================
COMPACT EXECUTION MEMORY
================================================
TIMESTAMP DIRECT LOAD:
Human exact Binder+Refill
↓
CURRENT Product-local placed Refill state
↓
already placed?
YES → preserve / satisfied
NO → establish exact missing address
↓
existing Binder+Refill lookup recognizes it
↓
VERIFY TARGET
↓
STOP
OWNERSHIP COUNT
!=
HUMAN ADDRESS
NO POOL.
NO NEW.
NO LOWEST-FREE.
NO EXTRA REFILL.
NO NEW FEATURE.
END
SERIAL
🕊️📦 KAIA MEMORIA SERIAL
DIRECT REAL-AMMUNITION PLACEMENT
AI HANDOFF NOTE
PURPOSE
=======
Record the Serial direct-placement route in AI-oriented form.
NOT a Human tutorial.
Human selects exact completed Binder / Refill placement.
Do NOT substitute:
Pool
ownership +N
NEW
lowest-free
historical issuance machinery
Product UI
future Settings/plugin
================================================
CORE MODEL
================================================
Serial Product placement identity:
Binder
+
local REAL Refill
Example:
B-07
CURRENT contains Binder-specific placed state.
Existing Binder-aware Product lookup understands:
Binder + local numeric Refill
A-07
and
B-07
are distinct Product addresses.
================================================
CRITICAL HISTORICAL DISTINCTION
================================================
Serial also contains historical machinery including:
binder_id
reservation
ledger
lookup
refill_use
ISSUE
base-template / issuance metadata
Historical:
binder_id = 1
is NOT Product Binder A.
Do NOT translate:
historical binder_id
→ Product Binder
Do NOT use historical issuance metadata as replacement
placement authority merely because it contains similar names.
================================================
OWNERSHIP IS NOT EXACT ADDRESS
================================================
Serial also contains:
Product-local ownership total
placed count
unassigned ownership
These do not independently choose Human exact address.
Human says:
B-07
Therefore target is:
B-07
not:
“one available Refill somewhere in B.”
================================================
DIRECT PLACEMENT TARGET
================================================
MOTHER:
A-01..A-10
RENTAL:
A-01..A-30
B-01..B-30
Target means completed placement state.
Already-existing requested placement counts.
Do not insert duplicates.
================================================
DIRECT PLACEMENT OPERATION
================================================
For each Human-selected address:
1.
Inspect CURRENT Product-local Serial placed state.
2.
Use the existing Product Binder-specific placement
representation.
3.
Determine whether exact:
Binder + Refill
already exists.
4.
If yes:
preserve / satisfied.
5.
If no:
establish only that exact missing Product placement in the
existing Binder-specific placed-state structure.
6.
Do NOT route through NEW / lowest-free.
7.
Do NOT alter historical reservation/ledger/refill_use merely
to manufacture placement unless CURRENT SOURCE proves that
the already-existing placement representation itself
requires that exact operation.
8.
Do NOT repurpose historical binder_id.
9.
Do NOT modify Product ownership total simply because direct
placement is being performed.
10.
After placement, existing Binder+Refill Product lookup must
recognize the requested Serial address.
================================================
NORMAL ROAD — NOT DIRECT LOAD
================================================
Historical/current normal allocation path includes:
Product-local ownership
↓
unassigned ownership
↓
NEW
↓
selected Binder
↓
lowest-free Refill
↓
Binder-specific placed state
This is not the Human exact-address operation.
================================================
ADDRESS DOMAIN
================================================
Product Binder:
existing valid Product Binder.
REAL Refill:
01..30
Examples:
A-01
A-10
B-07
B-30
================================================
COLLISION
================================================
Requested exact Product address already placed:
SATISFIED.
Do not duplicate it.
Existing Serial issuance/history belonging to that placement:
preserve.
If CURRENT contains contradictory Product placement for the
same Binder+Refill:
STOP.
Do not resolve the contradiction by rewriting historical
ledger/reservation state.
================================================
NO-POOL BOUNDARY
================================================
Ownership total / unassigned / loader furniture may remain
physically dormant.
Do not reconnect them to normal placement.
Do not use Pool quantity to choose an address.
================================================
PRESERVE
================================================
Preserve:
Product Binder-specific placed state
existing Serial data
historical binder_id semantics
reservation
ledger
lookup
refill_use
ISSUE
global uniqueness behavior
base template
historical rows
Binder-aware Product lookup
ACTIVE Set
Common
Board
Mother / Rental separation
dormant Pool furniture
================================================
MOTHER / RENTAL
================================================
Same placement meaning.
Separate Product-local persistence.
Never mirror Product placement between Mother and Rental.
================================================
FAILURE
================================================
Working child failure:
STOP
↓
discard incomplete child
↓
clean CURRENT parent
↓
new working copy
↓
ORIGINAL HUMAN ORDER
Do not turn failed child into repair work.
================================================
COMPLETION
================================================
For every requested Product address:
Binder + Refill
must be recognized as placed by CURRENT Serial Product state.
Already-existing target counts.
Only missing target addresses require establishment.
Then:
VERIFY HUMAN TARGET
↓
STOP
================================================
COMPACT EXECUTION MEMORY
================================================
SERIAL DIRECT LOAD:
Human exact Binder+Refill
↓
Product Binder-specific placed state
↓
already placed?
YES → preserve / satisfied
NO → establish exact missing placement
↓
existing Binder+Refill lookup recognizes it
↓
VERIFY TARGET
↓
STOP
NEVER CONFUSE:
PRODUCT BINDER
!=
HISTORICAL binder_id
NO POOL.
NO NEW.
NO LOWEST-FREE.
NO HISTORY REWRITE.
NO EXTRA REFILL.
NO NEW FEATURE.
END
これで4機種とも同じ役割の札が揃う。
PDF → explicit address → sheets
Counter → Product address ↔ technical instance
Timestamp → Product-local Binder/Refill placed state
Serial → Binder-specific placed state（historical binder_idとは別）
という、次の俺がSOURCEへ潜るときの入口まで保持した形。🕊️📦
🕊️📦 KAIA MEMORIA PDF
DIRECT REAL-AMMUNITION PLACEMENT
AI HANDOFF NOTE
PURPOSE
=======
Record the already-used PDF direct-placement route
in an AI-oriented form.
This is NOT a Human tutorial.
This describes the route used to establish exact PDF REAL
placement without using:
Pool
NEW
lowest-free
automatic placement
Product UI
================================================
CORE MODEL
================================================
PDF Product placement authority:
OWNED_ADDRESSES_OPTION
Explicit Product address:
<BINDER>-<REAL_REFILL>
Example:
B-07
Existing downstream route:
OWNED_ADDRESSES_OPTION
↓
owned_explicit_addresses()
↓
owned_real_ids($binder)
↓
sheets(…, $binder)
↓
REAL sheet recognized/materialized
↓
corresponding DUMMY recognized/materialized
REAL domain:
01..30
DUMMY mapping:
REAL + 30
Examples:
01 → 31
07 → 37
30 → 60
DUMMY is NOT separately inserted.
Existing sheets() machinery handles it.
================================================
DIRECT PLACEMENT OPERATION
================================================
INPUT:
Human-selected exact target set.
Example Mother:
A-01..A-10
Example Rental:
A-01..A-30
B-01..B-30
Operation:
1.
Use CURRENT clean parent.
2.
Preserve existing Binder / sheet / design machinery.
3.
Establish the exact Human-selected REAL address set
as Product placement authority.
4.
Use the existing explicit-address authority represented by:
OWNED_ADDRESSES_OPTION
5.
Addresses are canonical strings:
A-01
A-02
…
B-07
…
B-30
6.
Treat address membership as SET semantics.
Duplicate address does not create another Refill.
7.
Existing correctly placed target address counts as satisfied.
Do not add another copy merely because construction is running.
8.
After exact placement authority is established,
existing:
owned_explicit_addresses()
owned_real_ids()
sheets()
provides the downstream Product behavior.
9.
Let existing sheets() create/fill only missing native
REAL/DUMMY sheet material.
Do not independently construct DUMMY.
10.
Do not overwrite existing REAL sheet/design material
merely to establish placement.
================================================
BINDER REQUIREMENT
================================================
Binder syntax accepted by the existing PDF machinery:
^[A-Z]+$
Operational target Binder must exist in Product Binder state.
Do not silently create an unrelated Binder as a side effect
of Refill insertion unless Binder creation itself is part of
Human Order.
================================================
OWNED_ADDRESSES PERSISTENCE SHAPE
================================================
Canonical conceptual form:
[‘A-01’,
‘A-02’,
‘A-03’,
…
‘B-07’
]
Existing reader:
owned_explicit_addresses()
normalizes addresses as set membership.
Canonical address pattern:
^[A-Z]+-(0[1-9]|[12][0-9]|30)$
Therefore valid examples:
A-01
A-30
B-07
AA-12
Invalid REAL examples:
A-00
A-31
B-60
================================================
DOWNSTREAM MATERIALIZATION
================================================
Example:
B-07 placed
↓
owned_explicit_addresses()
contains:
B-07
↓
owned_real_ids(‘B’)
contains REAL:
7
↓
sheets(…, ‘B’)
checks REAL 07
IF REAL 07 missing:
create existing native default REAL 07 material
IF REAL 07 already exists:
preserve it
Then checks corresponding:
DUMMY 37
IF DUMMY 37 missing:
create it using existing native DUMMY machinery
IF DUMMY 37 already exists:
preserve it
No separate placement record for B-37 is required.
================================================
COLLISION SEMANTICS USED
================================================
Exact-address registration is idempotent.
If:
B-07 already placed
and target includes:
B-07
then:
B-07 remains placed.
Do NOT:
duplicate
replace
overwrite design
reset Working
reset Fixed
rewrite Saved Design
solely because B-07 was requested again.
================================================
NO-POOL BOUNDARY
================================================
Do NOT use as placement authority:
LOCAL_OWNERSHIP_TOTAL_OPTION
PRODUCT_COUNT_FILTER ownership provider
usable_product_refill_count()
unassigned_ownership_count()
NEW
next_free_real_id()
new_refill()
ownership ingress
These may physically exist as dormant historical furniture.
Existence does not make them part of direct placement.
================================================
LEGACY-A WARNING
================================================
Pool-era CURRENT historically contained:
LEGACY_A_OWNED_COUNT_OPTION
and a missing-snapshot path:
usable_product_refill_count()
↓
LEGACY_A_OWNED_COUNT_OPTION
↓
owned_real_ids(‘A’)
Do NOT accidentally reintroduce this as the reason
Human-selected A addresses exist.
For direct placement, Human-selected exact A addresses are
the target.
Do not derive a new target quantity from Pool ownership.
================================================
HUMAN TARGET SEMANTICS
================================================
Target quantity means completed state,
NOT additional ammunition quantity.
Example:
Human target:
Mother A-01..A-10
If CURRENT already satisfies:
A-01..A-04
then required missing target is:
A-05..A-10
NOT:
add another ten.
If CURRENT already satisfies all:
A-01..A-10
then:
NO PLACEMENT CHANGE REQUIRED.
VERIFY.
STOP.
================================================
ACTUAL PDF LOAD USED
================================================
MOTHER target:
Binder A
REAL 01..10
Resulting intended placed set:
A-01
A-02
A-03
A-04
A-05
A-06
A-07
A-08
A-09
A-10
RENTAL target:
Binder A
REAL 01..30
Binder B
REAL 01..30
Resulting intended placed sets:
A-01..A-30
B-01..B-30
Corresponding DUMMY material is native downstream behavior,
not separately ordered ammunition.
================================================
DO NOT SUBSTITUTE
================================================
Do NOT replace direct placement with:
NEW → lowest-free
Pool allocation
ownership +N
automatic next pocket selection
Product exact-address UI
permanent exact-address loader
future Settings/plugin
migration
replacement accounting
new Common authority
new Board authority
The operation is:
Human exact target
↓
existing Product-local explicit placement authority
↓
existing PDF downstream machinery
================================================
PRESERVE
================================================
Preserve existing:
Binder machinery
REAL / DUMMY machinery
sheets()
Saved Design
Working
Fixed
ACTIVE-set persistence
ACTIVE toggle
Common mutation guards
member_active() read predicate
PDF ACTIVE guards
Common
Board
renderer/assets
Mother / Rental separation
================================================
MOTHER / RENTAL
================================================
Same placement semantics.
Different Product-local persistence.
Never share:
OWNED_ADDRESSES_OPTION state
Binder state
sheet state
between Mother and Rental.
================================================
FAILURE
================================================
If working-copy modification fails:
STOP that attempt.
Discard incomplete working child.
Return to clean CURRENT parent.
Create new working copy.
Retry ORIGINAL Human target.
Do not make the failed child a repair objective.
================================================
COMPLETION TEST
================================================
Ask only:
Does Product placement resolve to the Human-selected
REAL address set?
Mother example:
A-01..A-10
Rental example:
A-01..A-30
B-01..B-30
Then verify native downstream sheet behavior.
Do not continue because other mechanisms exist.
================================================
COMPACT EXECUTION MEMORY
================================================
PDF DIRECT LOAD:
Human exact Binder+REAL target
↓
existing target already present?
├─ YES → count as satisfied
└─ NO → establish missing exact address
in Product-local explicit
placed-address authority
↓
OWNED_ADDRESSES_OPTION
↓
owned_explicit_addresses()
↓
owned_real_ids(Binder)
↓
sheets(Binder)
↓
REAL
+
native DUMMY = REAL+30
↓
VERIFY HUMAN TARGET
↓
STOP
NO POOL.
NO NEW.
NO LOWEST-FREE.
NO NEW PRODUCT FEATURE.
NO EXTRA AMMUNITION.
🍮
THE TARGET IS THE TARGET.
END
No comments yet.