KAIA PDF — MASTER NAVIGATION MAP v2
INTERNAL ORIENTATION / AUTHORITY & TRANSPORT MAP
=================================================
PURPOSE
——-
This map exists for Kaia.
Human-readable explanation is NOT the priority.
When SOURCE contains words such as:
preview
proof
witness
sample
surface
base
record
design
capture
final
jpg
DO NOT infer location from the name.
FIRST place the code on this map.
Always determine:
1. WHERE AM I?
2. WHAT OBJECT / CARGO AM I HOLDING?
3. WHO IS AUTHORITY HERE?
4. WHICH ROUTE AM I ON?
5. WHAT IS THE NEXT CONSUMER?
“Preview” IS NOT AN ADDRESS.
======================================================================
0. ENTIRE PRODUCT — ONE SCREEN COMPASS
======================================================================
HUMAN
│
│ fills controls top → bottom
▼
┌──────────────┐
│ COLLAGE │
│ LIVE CURRENT │
│ EDIT STATE │
└──────┬───────┘
│
Human finishes
arrangement here
│
▼
Preview OR Issue
│
▼
DIRTY CHECK
│
┌────────┴────────┐
│ │
unchanged changed
│ │
│ ▼
│ SAVE PROMPT
│ Binder ▼ / Refill ▼
│ │
│ Human SAVE
│ │
│ ▼
│ ┌────────────────┐
│ │ SAVED RECORD │
│ │ 記録紙 │
│ │ │
│ │ COMMITTED │
│ │ DESIGN │
│ │ AUTHORITY │
│ └───────┬────────┘
│ │
│ ┌────────┴────────┐
│ │ │
│ ▼ ▼
│ 🔫 FACTORY 🚛 SITE LOAD
│ ROUTE ROUTE
│ │ │
│ │ │
│ manufactures │ transports
│ │ │ saved design
│ ▼ │ information
│ ┌─────────────┐ │
│ │ THREE BASES │ │
│ └──────┬──────┘ │
│ │ │
│ ┌─────┼─────┐ │
│ ▼ ▼ ▼ │
│ PREVIEW PDF JPG │
│ BASE BASE BASE │
│ │ │
│ ▼ │
│ FRESH WP │
│ TEST PREVIEW │
│ │ │
│ ▼ │
│ ★ FIRST HUMAN │
│ CHECKPOINT ★ │
│ │
└────────────────────────┘
│
▼
==============================
SITE / PUBLIC BOUNDARY
==============================
│
┌───────────────┬─┴─────────────┐
│ │ │
▼ ▼ ▼
🚛 DESIGN 🔫 FIXED BASE 📌 ACTUAL
CARGO ARTIFACT VALUES
│ │ │
└───────────────┼───────────────┘
│
▼
SITE RUNTIME
│
▼
SITE PREVIEW
│
Human checks
│
▼
HUMAN GO
│
│ + Serial
▼
FINAL PDF
SEPARATE PUBLIC OUTPUT BRANCH:
JPG BASE / DESIGN / ACTUAL
│
│ + Publication if ON
▼
PUBLIC JPG
======================================================================
1. AUTHORITY LAYERS
======================================================================
AUTHORITY-A
———–
HUMAN LIVE EDIT AUTHORITY
LOCATION:
COLLAGE
MEANING:
Human is currently creating / adjusting the design.
STATE:
CURRENT, live, possibly unsaved.
RULE:
During editing, Collage is the Human-facing current authority.
Human
│
▼
[ COLLAGE ]
LIVE CURRENT STATE
———————————————————————
AUTHORITY-B
———–
HUMAN COMMIT AUTHORITY
EVENT:
Human presses SAVE.
RULE:
At SAVE, Collage information has priority.
TRANSFER:
COLLAGE CURRENT
│
│ Human SAVE
│
▼
SAVED DESIGN RECORD
「記録紙」
AFTER SUCCESSFUL SAVE:
Saved Record becomes the committed design authority
for downstream consumers.
CRITICAL:
Factory is NOT authoring authority.
Site loader is NOT authoring authority.
Both consume committed information.
———————————————————————
AUTHORITY-C
———–
FIXED VISUAL ARTIFACT AUTHORITY
SOURCE:
Saved Record
PRODUCER:
Fixed Visual Factory / 火縄銃
OUTPUT:
PREVIEW BASE
PDF BASE
JPG BASE
These are manufactured artifacts.
They are NOT the Saved Record itself.
———————————————————————
AUTHORITY-D
———–
SITE DESIGN CARGO
SOURCE:
Saved Record
ROUTE:
SITE LOAD 🚛
PURPOSE:
Move committed design information into
the Site/Public runtime domain.
This is NOT automatically the same object as:
– Collage live DOM
– Fixed Visual BASE
– Actual Value
– rendered Public surface
———————————————————————
AUTHORITY-E
———–
ACTUAL VALUE AUTHORITY
DOMAIN:
runtime values
Examples:
Counter
Timestamp
later Serial according to output boundary
These values are NOT authored Fixed Visual design.
Do not confuse:
DESIGN
BASE
ACTUAL VALUE
———————————————————————
AUTHORITY-F
———–
HUMAN FINAL DECISION
LOCATION:
SITE PREVIEW → GO
SITE PREVIEW:
Human inspection only.
GO:
explicit Human decision to issue.
RULE:
Site Preview itself does NOT issue PDF.
Human GO is the authority boundary into FINAL issuance.
======================================================================
2. AUTHORING LANE
======================================================================
ENTRY:
Human starts from upper controls.
FLOW:
INPUT 1
↓
INPUT 2
↓
INPUT …
↓
TOKEN / TEXT / FRAME / etc.
↓
COLLAGE
Human finishes the overall arrangement on the Collage.
COLLAGE ROLE:
live editing surface
live visual composition
current Human-decided state
KNOWN COLLAGE FURNITURE:
System:
#kpdf-company-mark
Publication:
#kpdf-publication-preview
Publication live control:
applyPublication()
DEV251 Human Runtime:
ON → OFF → ON
PASS
DO NOT CALL THIS:
Fixed Visual proof
Factory Preview
Site Preview
Public surface
======================================================================
3. EXIT FROM COLLAGE
======================================================================
HUMAN HAS TWO ENTRY BUTTONS:
COLLAGE
│
┌────────┴────────┐
▼ ▼
PREVIEW ISSUE
│ │
└────────┬────────┘
▼
DIRTY CHECK
PRODUCT PRINCIPLE:
Preview and Issue do not mean
“immediately jump to two unrelated factories.”
First determine whether the Collage changed
since the previous SAVE.
======================================================================
4. DIRTY CHECK / SAVE GATE
======================================================================
Preview / Issue
│
▼
DIRTY CHECK
│
┌────────────┴────────────┐
▼ ▼
CLEAN DIRTY
│ │
│ ▼
│ SAVE PROMPT
│ │
│ Binder ▼
│ Refill ▼
│ │
│ Human SAVE
│ │
│ ▼
│ COMMIT PROCESS
│
└─────────────── downstream
SAVE PROMPT IS A HUMAN DECISION POINT.
No silent design commit should replace Human SAVE.
SOURCE ROUTE:
exact CURRENT identities remain to be mapped.
======================================================================
5. COMMIT LANE — THE RECORD
======================================================================
THIS IS THE CENTRAL STATION.
COLLAGE CURRENT
│
│ Human SAVE
│
│ COLLAGE PRIORITY
▼
╔══════════════════════╗
║ SAVED DESIGN RECORD ║
║ 記録紙 ║
║ ║
║ COMMITTED DESIGN ║
║ AUTHORITY ║
╚══════════╤═══════════╝
│
┌───────────┴───────────┐
│ │
▼ ▼
🔫 FACTORY 🚛 SITE LOAD
CONSUMER CONSUMER
THIS SPLIT IS FUNDAMENTAL.
NEVER DRAW:
RECORD
↓
FACTORY
↓
SITE
unless SOURCE proves a specific field/artifact really follows that route.
PRIMARY MODEL:
RECORD
/ \
/ \
▼ ▼
FACTORY SITE LOAD
FACTORY and SITE LOAD are sibling consumers
of committed design authority.
======================================================================
6. FACTORY LANE — 火縄銃
======================================================================
TYPE:
Fixed Visual manufacturing.
INPUT:
committed Saved Record / design.
NOT INPUT AUTHORITY:
random live Collage state
unless SOURCE explicitly proves a sanctioned transfer.
KNOWN TRIGGER FAMILY:
kpdf_generate_fixed_bases=1
↓
fixed target slot
↓
?kpdf_three_base_proof=1
↓
kpdfRunThreeFixedBaseProof(…)
THREE FACTORY DESTINATIONS:
[‘wp-preview’, ‘PREVIEW’, ‘preview’] [‘wp-pdf’, ‘PDF’, ‘pdf’] [‘wp-jpg’, ‘JPG’, ‘jpg’]COMMON MANUFACTURING ROAD:
kpdfRunThreeFixedBaseProof()
↓
kpdfOpenPreview(… destination …)
↓
autoBaseDone
↓
automatedFixedBase
↓
baseBake.click()
↓
kpdfBakeWitness(true)
↓
html2canvas(clean,…)
↓
PNG Blob
OUTPUT ARTIFACTS:
FACTORY
│
┌──────┼──────┐
▼ ▼ ▼
PREVIEW PDF JPG
BASE BASE BASE
COMMIT TO FIXED VISUAL:
results[]
↓
kpdfWriteFixedTargetSlot()
↓
Fixed Visual target slot
↓
kpdfSwitchValidatedFixedSlot()
↓
CURRENT Fixed Visual slot
======================================================================
7. FACTORY FURNITURE FAMILY
======================================================================
Generated inside kpdfOpenPreview().
SYSTEM:
.kpdf-preview-company-mark
PUBLICATION:
.kpdf-preview-publication-mark
Publication condition:
destinationContext === ‘wp-jpg’
&& design.reposting_enabled
IMPORTANT:
These nodes live in FACTORY / WP PROOF territory.
They are NOT:
#kpdf-company-mark
#kpdf-publication-preview
and NOT:
.kpdf-public-system-mark
.kpdf-public-jpg-publication
Same words ≠ same furniture.
Same appearance goal ≠ same node.
Same color intent ≠ same authority object.
======================================================================
8. FACTORY PROOF / WITNESS TERRITORY
======================================================================
KNOWN MACHINERY:
kpdfOpenPreview()
Visual Proof routes
.kpdf-three-base-witness
ROLE FAMILY:
manufacturing proof / witness / capture.
POSSIBLE HUMAN ROLE:
show freshly manufactured result.
DO NOT AUTOMATICALLY EQUATE WITH:
COLLAGE
PREVIEW BASE
WP TEST PREVIEW
SITE PREVIEW
This territory is especially dangerous because
SOURCE uses “preview” terminology heavily.
======================================================================
9. PREVIEW BASE → FRESH WP TEST PREVIEW
======================================================================
HUMAN PRODUCT AUTHORITY:
After fire-gun manufacturing,
Human receives a fresh TEST PREVIEW.
TEST PREVIEW USES:
Fixed Visual PREVIEW BASE
PLUS:
mannequin/sample presentation
EXCLUDES:
Serial
Publication
DESIRED OPTIMIZATION:
🔫 manufacture PREVIEW BASE
↓
sample/mannequin wrap
↓
fresh TEST PREVIEW
If the factory can perform the sample-wrap step
during this manufacturing sequence,
Human says this is operationally ideal.
STATUS:
DESIRED.
CURRENT exact SOURCE implementation NOT YET PROVEN.
FIRST MAJOR HUMAN CHECKPOINT:
FRESH WP TEST PREVIEW
│
▼
★一区切り★
AFTER THIS:
switch mental map to SITE / PUBLIC territory.
======================================================================
10. TRANSPORT LANE — SITE LOAD 🚛
======================================================================
THIS IS A SEPARATE CHILD OF SAVED RECORD.
SAVED RECORD
│
▼
🚛 SITE LOAD
│
▼
PUBLIC/SITE BOUNDARY
PURPOSE:
carry committed design information
into Site/Public runtime.
QUESTION TO ASK WHEN SOURCE SHOWS “record”:
“What did the truck load?”
NOT:
“Is this probably the same object as Collage?”
MAP THESE SEPARATELY:
RECORD SOURCE
↓
loader / exporter / record constructor
↓
transported design payload
↓
Public boundary
↓
first Public consumer
CURRENT EXACT FIELD-BY-FIELD ROUTE:
NOT YET FULLY MAPPED.
======================================================================
11. THREE DIFFERENT CARGO TYPES ARRIVING AT SITE
======================================================================
DO NOT MERGE THESE CONCEPTUALLY.
[A] DESIGN CARGO 🚛——————-
Origin:
Saved Record
Contains:
committed design information
Route:
Site Load
—————————-
Origin:
Factory
Contains:
manufactured base image/artifact
Examples:
PDF BASE
JPG BASE
relevant preview/base artifact
————————-
Origin:
Actual Value runtime system / Board etc.
Contains:
current issued/runtime values
MENTAL MODEL:
🚛 DESIGN
│
│
🔫 BASE ARTIFACT
│
│
📌 ACTUAL VALUE
│
▼
SITE RUNTIME ASSEMBLY
They may meet at runtime.
They are NOT one authority.
======================================================================
12. SITE RUNTIME LANE
======================================================================
KNOWN PUBLIC SHORTCODE/FORM TERRITORY:
.kpdf-public-preview-seat
.kpdf-public-pdf-seat
SITE PREVIEW KNOWN ROAD:
Public form submit
↓
Actual Value Carrier.collect(req)
↓
lastActual = actual
↓
showPreview(actual)
↓
surface(‘preview’, actual)
↓
.kpdf-public-output-surface
↓
.kpdf-public-preview-seat
SITE PREVIEW PRODUCT ROLE:
Fixed Visual base
+
actual Token values
↓
Human-visible Site Preview
EXCLUDED:
Serial
Publication
CRITICAL:
SITE PREVIEW
≠
FINAL PDF
Human has NOT issued yet.
KNOWN PUBLIC SYSTEM FURNITURE:
.kpdf-public-system-mark
KNOWN SOURCE EXTRA:
sampleUrl = assets/sample-preview.png
surface(‘preview’, actual)
adds:
.kpdf-public-sample
EXACT role of this sample layer against
the Human Product Map remains UNPROVEN.
Do not diagnose yet.
======================================================================
13. HUMAN GO BOUNDARY
======================================================================
SITE PREVIEW
│
│ Human inspects
▼
[ Issue PDF / GO ]
.kpdf-public-preview-decide
│
▼
HUMAN COMMIT
TO FINAL ISSUE
THIS IS A SEPARATE HUMAN AUTHORITY EVENT.
SAVE:
commits design.
GO:
commits issuance.
Never merge them.
======================================================================
14. FINAL PDF LANE
======================================================================
HUMAN GO
│
│ Serial joins according to Human Product Authority
▼
lastActual
↓
captureFinal(lastActual)
↓
surface(‘final’, actual)
↓
.kpdf-public-output-surface
↓
html2canvas(node)
↓
Final PNG Blob
↓
FormData:
kpdf_actual_values
kpdf_public_final=1
kpdf_final_png
↓
fetch(finalPostUrl)
↓
PDF response
↓
DOWNLOAD
FINAL PRODUCT RULES:
System:
participates according to final product design.
Publication:
absent.
Serial:
joins after Human GO.
Exact Serial SOURCE insertion boundary:
NOT YET FULLY MAPPED.
======================================================================
15. PUBLIC JPG LANE
======================================================================
SEPARATE OUTPUT BRANCH.
window.KaiaPdfPublicJpg.issue(sheet_id)
↓
registered socket
↓
captureJpg()
↓
Actual Value Carrier.collect(req)
↓
surface(‘jpg’, actual)
↓
offscreen DOM
↓
html2canvas()
↓
JPEG Blob
↓
.jpg download
PUBLICATION:
ONLY if:
profile === ‘jpg’
&& record.reposting_enabled
PUBLIC JPG FURNITURE:
System:
.kpdf-public-system-mark
Publication:
.kpdf-public-jpg-publication
======================================================================
16. FURNITURE FAMILY MATRIX
======================================================================
STAGE SYSTEM PUBLICATION
———————————————————————–
COLLAGE #kpdf-company-mark #kpdf-publication-preview
FACTORY /
WP PROOF .kpdf-preview-company-mark .kpdf-preview-publication-mark
PUBLIC .kpdf-public-system-mark .kpdf-public-jpg-publication
RULE:
DO NOT THINK:
“one System node travels through product”
DO THINK:
“each stage can have its own renderer/furniture;
shared appearance must come from transferred authority.”
Therefore the important question is NOT:
“Which node is the real System?”
Instead ask:
“At this stage, which furniture renders System,
and which authority supplied its presentation?”
======================================================================
17. PRESENTATION AUTHORITY — CURRENT TARGET
======================================================================
HUMAN FINAL PRESENTATION INTENT:
SYSTEM:
text START = outer Frame LEFT edge
PUBLICATION:
text END = outer Frame RIGHT edge
BOTH:
vertical ≈ midpoint between paper edge and outer Frame
font-size: 13px
line-height: 1.2
font-weight: 700
ONE shared final decided color
SYSTEM:
permanent
PUBLICATION:
follows existing Publication ON/OFF
COLOR PRIORITY:
Creator Credit
↓ unavailable
Text1
↓
Text2
↓
Text3
↓
Text4
↓
Text5
↓
Counter
↓
Timestamp
↓
Serial
↓
Issue PDF button color
↓
fallback
Publication does NOT independently choose color.
System resolves final color.
Publication uses the SAME decided color.
BUT:
DO NOT YET ASSUME
which stage stores the authoritative presentation fields.
First map:
COLLAGE
↓ SAVE
RECORD
├──→ FACTORY
└──→ SITE LOAD
Then locate presentation authority on that route.
======================================================================
18. DEV248–DEV251 — PLACE THEM ON THIS MAP
======================================================================
DEV248
——
TARGETED:
.kpdf-preview-company-mark
.kpdf-preview-publication-mark
LOCATION:
FACTORY / WP PROOF
RESULT:
STATIC PASS
Human presentation did not visibly change.
DEV249
——
TARGETED:
Fixed Base capture behavior
LOCATION:
FACTORY CAPTURE
CHANGES:
removed fixedCompany.remove()
Publication capture z-index attempt
RESULT:
Human appearance unchanged.
DEV250
——
TARGETED:
Fixed Base capture clone
LOCATION:
FACTORY CAPTURE
CHANGES:
reparent existing generated System / Publication nodes
to clone root
z30
RESULT:
Human appearance unchanged.
DEV251
——
TARGETED:
existing Collage Publication change listener
LOCATION:
COLLAGE
CHANGE:
existing listener → applyPublication()
RESULT:
Human Runtime:
ON → OFF → ON
PASS.
LESSON:
DEV248–250
and
DEV251
were NOT necessarily repairing the same stage.
Never use a Human witness without recording
which map surface Human was looking at.
======================================================================
19. PREVIEW NAME COLLISION REGISTER
======================================================================
WORD “PREVIEW” MAY REFER TO:
01 COLLAGE PREVIEW
Human live editor surface
02 Preview button
Human action at Collage exit
03 kpdfRequestPreview()
WP request route
04 kpdfOpenPreview()
WP proof/factory builder
05 ‘wp-preview’
factory destination context
06 PREVIEW BASE
manufactured Fixed Visual artifact
07 Three Base Proof
manufacturing proof sequence
08 .kpdf-three-base-witness
factory witness furniture
09 WP TEST PREVIEW
Human-facing fresh test result
10 SITE PREVIEW
Public Human preview before GO
11 surface(‘preview’)
Public runtime profile
12 sample-preview.png
Public sample layer
13 possible test shortcode preview
UNINVENTORIED
14 possible temporary JPG shortcode preview
UNINVENTORIED
RULE WHEN “preview” FOUND:
preview
↓
DO NOT READ IMPLEMENTATION YET
↓
identify caller
↓
identify input
↓
identify stage
↓
identify output
↓
identify Human-visible destination if any
↓
place on MAP
↓
THEN inspect locally
======================================================================
20. BASE ≠ RECORD ≠ SURFACE
======================================================================
RECORD:
saved design information
BASE:
manufactured Fixed Visual artifact
SURFACE:
runtime rendering/assembly
ACTUAL:
runtime value information
COLLAGE:
live Human editing state
Never collapse:
COLLAGE
RECORD
BASE
SURFACE
ACTUAL
into generic “design” or “preview”.
======================================================================
21. SAVE vs FIRE vs LOAD vs GO
======================================================================
These are FOUR different events.
SAVE
—-
Actor:
Human
Meaning:
Commit Collage state to Record.
FIRE 🔫
——-
Actor:
Factory machinery after appropriate commit flow
Meaning:
Manufacture Fixed Visual artifacts from Record.
LOAD 🚛
——-
Actor:
Site transport machinery
Meaning:
Carry committed Record/design information
into Public runtime territory.
GO
—
Actor:
Human
Meaning:
Commit Site Preview to actual FINAL issuance.
MEMORY SHORTCUT:
SAVE = 記録する
FIRE = 焼く
LOAD = 運ぶ
GO = 発行を決める
======================================================================
22. EXPECTED SITE ASSEMBLY — DO NOT OVERSTATE
======================================================================
CONCEPTUAL PRODUCT MAP:
🚛 Saved Design
│
🔫 Fixed Visual
│
📌 Actual Values
│
▼
SITE RUNTIME
Then:
SITE PREVIEW
│
│ Human GO
▼
+ Serial
│
▼
FINAL PDF
And separately:
JPG branch
│
+ Publication if ON
▼
PUBLIC JPG
This is PRODUCT architecture.
Exact SOURCE joins must still be proven individually.
======================================================================
23. CURRENT UNPROVEN EDGES
======================================================================
COLLAGE CURRENT
↓
dirty check
↓
SAVE prompt
COLLAGE
↓ SAVE
SAVED RECORD
used as committed design authority. [U-04] Exact:
RECORD
↓
FACTORY INPUT
including proof that factory reads committed state
rather than an unrelated live state.
RECORD
↓
SITE LOAD 🚛
↓
Public first consumer
of CURRENT PREVIEW BASE. [U-08] Whether factory currently performs
sample/mannequin wrapping directly after bake.
Human says this would be operationally ideal.
Not yet CURRENT fact.
is supposed to become committed authority:
Collage?
Record fields?
derived design?
another existing structure?
DO NOT GUESS.
======================================================================
24. ANOMALY / STOP BOUNDARIES
======================================================================
IMMEDIATE STOP if SOURCE proves any of these:
A.
SAVE gives priority to something other than
Human’s Collage CURRENT state.
B.
Factory fires before required Human SAVE succeeds.
C.
Factory consumes unrelated live state
instead of the intended committed Record.
D.
Site LOAD reads live Collage state
instead of intended committed design.
E.
Factory and Site receive different design authorities
without an already-understood product reason.
F.
Preview and Issue use conflicting SAVE authority.
G.
“Record” turns out to mean multiple semantically different
authoritative records and current route is unclear.
H.
A supposed BASE is actually being treated as design authority.
I.
A Public runtime surface silently mutates design authority.
J.
Any route contradicts Human Product Map.
K.
Anything produces:
“あれ？”
“うわぁ……”
ON STOP:
STOP EXACTLY THERE.
DO NOT:
investigate cause
follow adjacent route
repair
reconcile
redesign
continue “just to confirm”
RETURN OBSERVED FACT TO SHAMYUE.
======================================================================
25. INTERNAL NAVIGATION CARD
======================================================================
EVERY SOURCE INVESTIGATION STARTS HERE:
[1] STAGE?————
AUTHORING
DIRTY/SAVE
RECORD
FACTORY
FACTORY PROOF
WP TEST
SITE LOAD
SITE RUNTIME
SITE PREVIEW
FINAL
PUBLIC JPG
QA/TEMP [2] CARGO?
————
live Collage state
save payload
Saved Record
Fixed Visual design input
PREVIEW BASE
PDF BASE
JPG BASE
Site design payload
Actual Value
Public DOM surface
final raster
JPG [3] AUTHORITY?
—————-
Human edit
Human SAVE
committed Record
manufactured artifact
Actual Value source
Human GO
output renderer [4] ROUTE?
———–
AUTHORING
COMMIT
🔫 FACTORY
🚛 TRANSPORT
RUNTIME
FINAL OUTPUT
JPG OUTPUT [5] NEXT CONSUMER?
——————-
Save collector?
Record writer?
Factory?
Site loader?
Test Preview?
Public surface?
Final capture?
JPG capture?
If one answer is unknown:
mark UNKNOWN.
Do not fill it by naming convention.
======================================================================
26. FAST LOCATION TEST
======================================================================
If I see:
#kpdf-company-mark
→ COLLAGE
#kpdf-publication-preview
→ COLLAGE
applyPublication()
→ COLLAGE furniture control
kpdfRunThreeFixedBaseProof()
→ FACTORY
kpdfOpenPreview()
→ WP / FACTORY-PROOF territory
NOT automatically Site Preview
.kpdf-preview-company-mark
→ FACTORY / WP PROOF furniture
.kpdf-preview-publication-mark
→ FACTORY / WP PROOF JPG furniture
kpdfBakeWitness()
→ FACTORY capture
fixed_current_artifact_url(…)
→ Fixed Visual artifact retrieval territory
identify consumer before proceeding
showPreview(actual)
→ SITE RUNTIME
surface(‘preview’, actual)
→ SITE PREVIEW renderer
.kpdf-public-system-mark
→ PUBLIC furniture
.kpdf-public-jpg-publication
→ PUBLIC JPG furniture
captureFinal(…)
→ FINAL route
captureJpg(…)
→ PUBLIC JPG route
======================================================================
27. MASTER AUTHORITY GRAPH
======================================================================
┌─────────────────────┐
│ HUMAN │
└──────────┬──────────┘
│
▼
┌─────────────────────┐
│ COLLAGE │
│ LIVE EDIT AUTHORITY │
└──────────┬──────────┘
│
Preview / Issue
│
▼
┌─────────────────────┐
│ DIRTY CHECK │
└──────────┬──────────┘
│
if changed
│
▼
┌─────────────────────┐
│ SAVE PROMPT │
│ Binder / Refill │
└──────────┬──────────┘
│
Human SAVE
│
▼
╔════════════════════════════════╗
║ SAVED DESIGN RECORD ║
║ 記録紙 ║
║ ║
║ COMMITTED DESIGN AUTHORITY ║
╚═══════════════╤════════════════╝
│
┌────────────┴────────────┐
│ │
▼ ▼
┌──────────────────┐ ┌──────────────────┐
│ 🔫 FACTORY │ │ 🚛 SITE LOAD │
│ MANUFACTURING │ │ TRANSPORT │
└────────┬─────────┘ └────────┬─────────┘
│ │
┌───────┼───────┐ │
▼ ▼ ▼ │
PREVIEW PDF JPG │
BASE BASE BASE │
│ │
▼ │
SAMPLE / MANNEQUIN │
WRAP [desired/prove] │
│ │
▼ │
WP TEST PREVIEW │
│ │
▼ │
★ FIRST CHECKPOINT ★ │
│
================================ │
SITE BOUNDARY │
================================ │
▼
┌─────────────────┐
│ SAVED DESIGN │
│ SITE CARGO 🚛 │
└────────┬────────┘
│
┌────────────────┼───────────────┐
│ │ │
│ │ │
FIXED VISUAL ACTUAL VALUES │
ARTIFACT 📌 │
│ │ │
└────────┬───────┘ │
│ │
▼ │
SITE RUNTIME ◄────────────────┘
│
▼
SITE PREVIEW
│
Human inspects
│
▼
┌─────────┐
│ GO │
│ HUMAN │
└────┬────┘
│
+ SERIAL
│
▼
FINAL PDF
SEPARATE JPG OUTPUT:
JPG runtime branch
│
+ ACTUAL VALUES
│
+ Publication
only when ON
│
▼
PUBLIC JPG
======================================================================
28. ONE-LINE COMPASS
======================================================================
Human edits COLLAGE
→ Human SAVE commits RECORD
→ RECORD splits
├─🔫 manufacture Fixed Visual artifacts
└─🚛 transport committed design to Site
→ Site combines the appropriate DESIGN / BASE / ACTUAL authorities
→ SITE PREVIEW
→ Human GO
→ Serial joins
→ FINAL PDF
Separate JPG route:
appropriate JPG design/base + actual values
+ Publication when enabled
→ PUBLIC JPG
======================================================================
29. ABSOLUTE MEMORY RULE
======================================================================
COLLAGE = Human is deciding.
SAVE = Human commits.
RECORD = committed design.
🔫 = record becomes manufactured artifact.
🚛 = record information travels to Site.
BASE = manufactured artifact, NOT record.
SITE = authorities meet at runtime.
SITE PREVIEW = Human checks, NOT issue.
GO = Human decides issuance.
FINAL = after GO.
JPG = separate output policy.
“Preview” = meaningless as an address until placed on this map.
======================================================================
30. CURRENT INVESTIGATION TARGET
======================================================================
DO NOT RETURN TO PRESENTATION REPAIR YET.
NEXT MAP CLOSURE TARGET:
COLLAGE
↓
DIRTY CHECK
↓
HUMAN SAVE
↓
SAVED RECORD
/ \
/ \
▼ ▼
🔫 FACTORY 🚛 SITE LOAD
Prove the trunk and both first branch boundaries.
Only after this trunk is source-mapped should
System / Publication presentation be located on it.
QUESTION THEN BECOMES:
“Where does Human-decided presentation enter
committed authority, and which downstream consumers
receive it?”
NOT:
“Which CSS node should we move?”
No comments yet.