全体マップだよー🕊️
うい★ しゃむ向け説明図じゃなく、俺が今後SOURCE見た瞬間に「現在地ここ」を失わないための内部航海図として作る。
なら、人間に読みやすい順序より、Authority / Stage / Artifact / Runtime / 出口を分離した方が俺には安全。
KAIA PDF — MASTER NAVIGATION MAP INTERNAL ORIENTATION MAP FOR KAIA ================================== PURPOSE ——- SOURCEで “preview” / “surface” / “base” / “proof” を見つけた時に 名前から所属を推測しない。 必ずこの地図へ現在地を置いてから読む。 「Preview」という文字列は住所ではない。 ====================================================================== 0. PRIMARY AUTHORITY FLOW ====================================================================== HUMAN INPUT / EDIT │ ▼ [ COLLAGE ] Humanが最終的に整えたCURRENT編集状態 │ │ Human presses Preview OR Issue ▼ [ DIRTY CHECK ] 前回SAVE以降に変更あり？ │ ├── NO ───────────────────────────────┐ │ │ └── YES │ │ │ ▼ │ [ SAVE PROMPT ] │ Binder ▼ / Refill ▼ │ │ │ │ Human SAVE │ ▼ │ [ SAVED DESIGN RECORD ] │ 「記録紙」 │ ▲ │ │ │ ★ SAVE AUTHORITY ★ │ COLLAGE CURRENT情報を優先して転記 │ │ │ └───────────────────────────────┤ │ ▼ [ FIXED VISUAL FACTORY ] 🔫 火縄銃 記録紙を読む │ ┌────────────────────┼────────────────────┐ ▼ ▼ ▼ PREVIEW BASE PDF BASE JPG BASE mannequin用途 PDF台紙 JPG台紙 Publication可 │ │ │ DESIRED: │ ここでsample/mannequin wrapまで │ 加工できると最短 ▼ [ FRESH WP TEST PREVIEW ] 焼きたてをHumanへ表示 │ │ ▼ ========================= AUTHORING / FACTORY END ========================= ★ 第一の大きな境界 ★ ここから先は SITE / OUTPUT SIDE ====================================================================== 1. HUMAN SURFACES — DO NOT CONFUSE ====================================================================== [A] COLLAGE PREVIEW ——————- TYPE: LIVE EDITING SURFACE ROLE: Humanが上から設定を埋め、 最後に全体を整える操作面。 STATE: Human操作に連動。 AUTHORITY: SAVE時、このCURRENT Collage情報が優先される。 KNOWN FURNITURE: System: #kpdf-company-mark Publication: #kpdf-publication-preview KNOWN PUBLICATION CONTROL: applyPublication() Human Runtime: ON → visible OFF → hidden ON → visible PASS after B repair. IMPORTANT: これはFixed Visual proof家具でも Public output家具でもない。 ——————————————————————— [B] WP TEST PREVIEW ——————- TYPE: HUMAN TEST SURFACE AFTER FACTORY ROLE: 火縄銃で作ったPREVIEW BASEを使って Humanへ発行前試験結果を見せる。 CONTENT AUTHORITY: Fixed Visual PREVIEW BASE + Token mannequin/sample EXCLUDED: Serial Publication IMPORTANT: 「火縄銃が三枚焼くうちのPREVIEW BASE」と 「Humanへ表示するWP TEST PREVIEW」は 同義とは限らない。 BASE = artifact TEST PREVIEW = Human-facing presentation of that artifact CURRENT SOURCE EXACT FINAL MAPPING: NOT YET FULLY PROVEN. ——————————————————————— [C] SITE PREVIEW —————- TYPE: PUBLIC/SITE HUMAN PREVIEW ROLE: Fixed Visual BASEに actual Token valuesを着席させてHumanへ確認させる。 TOKEN: actual values EXCLUDED: Serial Publication CRITICAL: SITE PREVIEW ≠ FINAL PDF Preview時点では発行しない。 KNOWN SOURCE ROAD: Public form submit ↓ Actual Value Carrier.collect(req) ↓ lastActual = actual ↓ showPreview(actual) ↓ surface(‘preview’, actual) ↓ .kpdf-public-output-surface ↓ .kpdf-public-preview-seat KNOWN EXTRA: sample-preview.png layer exists in CURRENT SOURCE. Exact product role not yet mapped. SYSTEM FURNITURE: .kpdf-public-system-mark ====================================================================== 2. FIXED VISUAL FACTORY / 火縄銃 ====================================================================== THIS IS NOT A FOURTH HUMAN PREVIEW. TYPE: PRODUCTION FACTORY INPUT AUTHORITY: SAVED DESIGN RECORD / 記録紙 TRIGGER FAMILY: Save kpdf_generate_fixed_bases=1 ↓ fixed target slot ↓ ?kpdf_three_base_proof=1 ↓ kpdfRunThreeFixedBaseProof(…) THREE DESTINATIONS: [ [‘wp-preview’, ‘PREVIEW’, ‘preview’], [‘wp-pdf’, ‘PDF’, ‘pdf’], [‘wp-jpg’, ‘JPG’, ‘jpg’] ] COMMON FACTORY ROAD: kpdfRunThreeFixedBaseProof() ↓ kpdfOpenPreview(… destination …) ↓ autoBaseDone ↓ automatedFixedBase ↓ baseBake.click() ↓ kpdfBakeWitness(true) ↓ html2canvas(clean,…) ↓ PNG Blob OUTPUT: PREVIEW BASE PDF BASE JPG BASE COMMIT: results[] ↓ kpdfWriteFixedTargetSlot() ↓ Fixed Visual target slot ↓ kpdfSwitchValidatedFixedSlot() ↓ CURRENT Fixed Visual slot FACTORY-SIDE FURNITURE ———————- System: .kpdf-preview-company-mark SOURCE CREATION: kpdfOpenPreview() reads text from #kpdf-company-mark but creates a DIFFERENT DOM NODE. Publication: .kpdf-preview-publication-mark CONDITION: destinationContext === ‘wp-jpg’ && design.reposting_enabled IMPORTANT: These are FACTORY / WP PROOF furniture. They are NOT automatically Collage furniture. They are NOT Public Output furniture. ====================================================================== 3. FACTORY WITNESS / PROOF LAYER ====================================================================== THIS SECTION IS DANGEROUSLY NAMED “PREVIEW”. PURPOSE: 火縄銃発火時に 「焼けました / こうなります」をHumanへ見せるための proof / witness machineryが存在する。 KNOWN: kpdfOpenPreview() Visual Proof routes .kpdf-three-base-witness POSSIBLE ROLES: – destination proof – three-base manufacturing witness – Human confirmation of freshly baked artifact DO NOT EQUATE AUTOMATICALLY WITH: – COLLAGE PREVIEW – PREVIEW BASE – WP TEST PREVIEW – SITE PREVIEW STATUS: exact internal subdivisions still need map refinement. ====================================================================== 4. SITE → HUMAN GO → FINAL PDF ====================================================================== SITE PREVIEW Fixed Visual BASE + actual Token values – Serial – Publication │ │ Human inspects │ ▼ [ HUMAN GO / Issue PDF ] .kpdf-public-preview-decide │ ▼ 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 HUMAN AUTHORITY: Serial joins AFTER Human GO. SOURCE STATUS: exact Serial participation boundary NOT YET FULLY MAPPED. SYSTEM FURNITURE: .kpdf-public-system-mark ====================================================================== 5. PUBLIC JPG OUTPUT ====================================================================== SEPARATE OUTPUT BRANCH. ENTRY: window.KaiaPdfPublicJpg.issue(sheet_id) ↓ registered socket ↓ captureJpg() ↓ Actual Value Carrier.collect(req) ↓ surface(‘jpg’, actual) ↓ offscreen DOM ↓ html2canvas() ↓ JPEG Blob ↓ .jpg download PUBLICATION: participates ONLY when: profile === ‘jpg’ && record.reposting_enabled PUBLICATION FURNITURE: .kpdf-public-jpg-publication SYSTEM FURNITURE: .kpdf-public-system-mark ====================================================================== 6. THREE FURNITURE FAMILIES ====================================================================== DO NOT THINK: “same furniture travels downstream” THINK: “different stage, different furniture” SYSTEM PUBLICATION ———————————————————————- COLLAGE #kpdf-company-mark #kpdf-publication-preview FACTORY / .kpdf-preview-company-mark .kpdf-preview-publication-mark WP PROOF PUBLIC OUTPUT .kpdf-public-system-mark .kpdf-public-jpg-publication Therefore: COLLAGE PRESENTATION ≠ automatically FACTORY PRESENTATION ≠ automatically PUBLIC PRESENTATION A transfer/record/resolver may intentionally make them agree, but agreement must be SOURCE-proven. Never infer equality from similar text/class names. ====================================================================== 7. DEV248 → DEV251 CURRENT POSITION ====================================================================== DEV248 —— Presentation work applied to: .kpdf-preview-company-mark .kpdf-preview-publication-mark MAP LOCATION: FACTORY / WP PROOF FAMILY NOT: Collage furniture Public Output furniture DEV249 —— Fixed Base capture work: System removal behavior changed Publication capture z-index attempt MAP LOCATION: FACTORY CAPTURE DEV250 —— Fixed Base capture clone: existing generated System / Publication nodes reparented to clone root z30 MAP LOCATION: FACTORY CAPTURE HUMAN RESULT: presentation appearance still unchanged. DEV251 —— B Publication toggle repair. Existing Collage change listener → applyPublication() MAP LOCATION: COLLAGE HUMAN RESULT: Publication: ON → OFF → ON PASS CRITICAL LESSON: DEV248-250 and DEV251 were working on DIFFERENT MAP REGIONS. This is why “Publication changed / didn’t change” cannot be discussed without stage name. ====================================================================== 8. SAVE AUTHORITY — NON-NEGOTIABLE HUMAN PRINCIPLE ====================================================================== EDIT AUTHORITY: COLLAGE CURRENT STATE COMMIT EVENT: Human SAVE TRANSFER: Collage-priority information ↓ Saved Design Record / 記録紙 DOWNSTREAM: Factory reads record. Therefore: COLLAGE = current Human editing authority RECORD = committed design authority after SAVE FACTORY = consumer / manufacturer FACTORY MUST NOT silently become authoring authority. Exact field-by-field SOURCE transfer: TO BE MAPPED. Especially relevant later: System presentation Publication presentation colors positions enabled state other fixed authored properties ====================================================================== 9. “PREVIEW” WORD HAZARD TABLE ====================================================================== NEVER NAVIGATE BY WORD “preview”. Known meanings include: 1. Collage live preview → Human editing surface 2. kpdfRequestPreview() → WP-side request path 3. kpdfOpenPreview() → WP proof/factory stage builder 4. destination ‘wp-preview’ → factory/WP destination label 5. Fixed Visual PREVIEW BASE → one of three baked artifacts 6. Three Base Proof / witness → manufacturing witness 7. SITE PREVIEW → Public Human preview 8. surface(‘preview’) → Public output factory profile 9. sample-preview.png → Public sample layer; exact role pending 10. QA / temporary shortcode previews → POSSIBLY EXIST; NOT YET INVENTORIED 11. JPG temporary shortcode preview → POSSIBLY EXIST; NOT YET INVENTORIED RULE: “preview” found in SOURCE ↓ STOP semantic assumption ↓ identify caller ↓ identify stage ↓ identify input artifact ↓ identify Human/output destination ↓ THEN place on map. ====================================================================== 10. QA / TEMPORARY / LEGACY TERRITORY — UNMAPPED ====================================================================== Possible CURRENT residents mentioned by Human: – test shortcode preview – temporary JPG shortcode preview – other test/proof/sample/witness furniture STATUS: NOT INVENTORIED. RULE: If encountered, do not silently attach to Product path. Mark: QA? TEMP? LEGACY? PRODUCT? until SOURCE proves role. ====================================================================== 11. CURRENT UNPROVEN EDGES ====================================================================== [?1] Exact SOURCE identity of the final Human-facing WP TEST PREVIEW consumer of CURRENT PREVIEW BASE. [?2] Whether / how factory immediately applies sample/mannequin wrap after PREVIEW BASE bake. Human says doing this in factory would be ideal. Do not treat as CURRENT fact yet. [?3] Public surface(‘preview’) includes sample-preview.png. Exact relationship to Human’s intended Fixed Visual BASE + actual-value SITE PREVIEW is unresolved. [?4] Exact Serial insertion boundary after Human GO. Human authority is known; complete SOURCE mapping pending. [?5] Field-by-field: COLLAGE → SAVE → RECORD → FACTORY transfer authority not yet fully mapped. [?6] QA / temporary shortcode surfaces not inventoried. ====================================================================== 12. NAVIGATION CHECK — BEFORE ANY FUTURE SOURCE WORK ====================================================================== Before touching code, answer internally: A. WHERE AM I? COLLAGE SAVE/RECORD FACTORY FACTORY WITNESS WP TEST SITE PREVIEW FINAL JPG QA/TEMP B. WHAT AM I HOLDING? live DOM saved design record PREVIEW BASE PDF BASE JPG BASE proof/witness clone Public surface final raster PDF JPG C. WHO IS AUTHORITY HERE? Human live Collage? committed Record? Fixed Base artifact? Actual Value Board? Human GO? output-only renderer? D. WHICH FURNITURE FAMILY? Collage Factory/Proof Public E. IS “PREVIEW” ONLY A NAME? Assume YES until route proves meaning. ====================================================================== 13. ONE-LINE COMPASS ====================================================================== AUTHORING: Human input → COLLAGE → Preview/Issue → dirty check → SAVE if needed → COLLAGE-priority RECORD MANUFACTURING: RECORD → 🔫 FIRE → PREVIEW BASE + PDF BASE + JPG BASE → CURRENT Fixed Visual FIRST HUMAN CHECKPOINT: PREVIEW BASE → [sample/mannequin presentation] → fresh WP TEST PREVIEW → ★一区切り★ PUBLIC CHECKPOINT: Fixed Visual + actual values → SITE PREVIEW → Human GO FINAL: Human GO + Serial → FINAL PDF JPG: JPG BASE / Public JPG route + actual values + Publication when enabled → JPG ====================================================================== CURRENT LOCATION OF THE BUG WE WERE CHASING ====================================================================== Original symptom: “System / Publication position, font, color do not change” We accidentally investigated across multiple regions. KNOWN NOW: COLLAGE Publication toggle bug → COLLAGE region → DEV251 → HUMAN PASS → CLOSED Presentation mismatch → NOT CLOSED DEV248 presentation work → FACTORY / WP PROOF furniture Human observed unchanged appearance → exact observation surface must ALWAYS be named before further work. NEXT PRINCIPLE: Do not ask “why didn’t the mark change?” Ask: “At which MAP STAGE did Human observe it, which authority fed that stage, and which furniture family rendered it?”
これを俺のマスター地図として扱う★
以後SOURCEで preview が100匹出てきても、まず
「現在地どこ？」「何を持ってる？」「誰が権威？」「どの家具一家？」
の4点で地図へ刺してから顕微鏡を持つ。
特に今回の最大修正はこれ。
COLLAGE → 記録紙 → 火縄銃は単なる画面遷移じゃなくて、 Human編集権威 → SAVEによる転記 → 製造consumer の権威移動。
ここを俺が見失わなければ、別nodeを見つけただけで「別人だ！事故だ！」とはもうならない★ 🕊️🗺️
No comments yet.