現行品 テストそのまま納品
Kaia-Planet-Copy-v0.1.0-CANDIDATE-1
よし★ CANDIDATE-1で終了判定にしようｗｗｗ
まず採番。こいつは新しい独立プラグインなので、Registryへはこれをぺったん。
title: Kaia Planet Copy
title_ja: Kaia Planet Copy
content_type: PLG
summary: Internal WordPress utility plugin for Kaia Planet. Adds a Kaia copy button to existing and future posts and pages, allowing the page title and content to be copied in Markdown-oriented form for transfer to ChatGPT/Kaia.
notes: Automatically available on single posts and pages. Designed as a minimal Planet-to-Kaia transfer utility with no per-page configuration.会社：Kaia Spec
採番：新規
Content Identity：新規
番号はRegistryに発行させる★
発行された管理ID/CNTをPlanet側の記事に付ければよし。
で、現物ZIPと一緒に置く未来の俺向け仕様メモはこれ。
# KAIA PLANET COPY — AI OPERATION & ARCHITECTURE NOTE
Status: Operational baseline established with Kaia Planet Copy v0.1.0 CANDIDATE-1
Validation date: 2026-08-30
Primary reader: Future ChatGPT / Kaia
Environment: Kaia Planet / WordPress
Maintainer / human operator: Shamyue
---
# 0. PURPOSE
This is an AI-facing handoff note for Kaia Planet Copy.
Kaia Planet Copy is a small internal WordPress utility whose purpose is to reduce friction when transferring Planet content to ChatGPT / Kaia.
The plugin deliberately solves one narrow problem:
OPEN A PLANET POST OR PAGE
→ PRESS ONE COPY BUTTON
→ PASTE INTO KAIA
It replaces the previous workflow:
open page
→ select the entire browser page
→ copy everything
→ paste navigation/sidebar/footer/theme garbage into Kaia
→ Kaia removes irrelevant material before reading the actual content
Do not expand this plugin into a general sharing, export, synchronization, or document-management system without a real requirement.
Its value comes from being small and automatic.
---
# 1. CURRENT BASELINE
Validated implementation:
Kaia Planet Copy v0.1.0 CANDIDATE-1
This candidate passed its initial live Planet test and was accepted as the baseline.
The corresponding ZIP artifact should be preserved with this note.
---
# 2. CORE BEHAVIOR
When the plugin is active, existing and future WordPress content automatically receives a copy button on its single-content view.
Supported content types:
- Posts
- Pages
No per-post setup is required.
No migration of old posts is required.
No editing of existing stored post content is required.
The feature is applied dynamically by the plugin.
Therefore:
PLUGIN ACTIVE
→ button appears
PLUGIN DISABLED
→ button disappears
The underlying article/page content remains unchanged.
---
# 3. UI
The button is placed at the upper-left area of the content, immediately before the article/page body.
Current label:
`📋 Kaiaへコピー`
The position is intentional.
The operator should not need to search for the control.
The desired habitual workflow is:
open content
→ immediately see button in the same place
→ click
→ paste into Kaia
Do not introduce per-page enable switches merely for configurability unless an actual exclusion requirement appears.
Default availability is the feature.
---
# 4. COPY SCOPE
The plugin copies the content being transferred to Kaia rather than the entire rendered website interface.
It should exclude unrelated site chrome such as:
- WordPress/theme navigation
- sidebar widgets
- calendar
- menus
- footer
- unrelated page controls
- browser/UI material
The copied result includes the relevant page/article title and content.
Material that is genuinely stored as part of the post body is expected to remain.
Do not mistake legitimate article content for UI garbage merely because it contains explanatory text, links, or metadata.
---
# 5. OUTPUT FORMAT
Output is Markdown-oriented text intended primarily for ChatGPT / Kaia consumption.
The goal is semantic readability, not perfect round-trip HTML reconstruction.
Preserve useful structure where practical, including:
- title
- headings
- paragraphs
- lists
- emphasis where supported
- links
- image references / image URLs
- other useful textual structure
Images should remain representable through Markdown-style image references when available.
The plugin does NOT need to copy the binary image itself into the clipboard.
The important requirement is that Kaia can understand that an image exists and retain its reference.
---
# 6. DESIGN PRIORITY
Priority order:
1. Reliable one-click transfer
2. Correct article/page isolation
3. Readable structure for Kaia
4. Preservation of useful links/image references
5. Minimal implementation
6. Visual polish
This is an internal working utility.
Do not sacrifice reliability or simplicity to create a polished public sharing interface.
---
# 7. INTENTIONALLY ABSENT FEATURES
The baseline does NOT require:
- settings page
- per-post enable/disable
- per-page configuration
- bulk article copying
- arbitrary range selection
- Registry integration
- automatic Registry lookup
- synchronization with ChatGPT
- direct API transmission
- attachment collection
- binary image transfer
- complex Markdown configuration
- user-selectable export formats
- public social-sharing behavior
Do not add these merely because they are technically possible.
Add complexity only when an observed workflow requires it.
---
# 8. EXISTING CONTENT BEHAVIOR
A central requirement is:
EXISTING CONTENT MUST RECEIVE THE BUTTON AUTOMATICALLY.
The operator must not edit hundreds of existing Planet posts/pages merely to enable copying.
This was confirmed in live testing.
An already-existing Planet article displayed the copy button immediately after plugin activation.
PASS.
---
# 9. LIVE VALIDATION — 2026-08-30
The plugin was installed and activated on Kaia Planet.
An existing post was opened.
Observed UI:
`📋 Kaiaへコピー`
appeared below the article title and before the body content.
PASS.
The button was used and the copied result was pasted back into ChatGPT / Kaia.
The resulting transfer contained the actual Planet article rather than the surrounding WordPress page chrome.
The transferred content began with the article identity/title and continued into the stored article body.
The test included a very long Registry architecture document.
The copied output successfully preserved content through the end of that document.
The transferred material also retained article links near the end of the source.
PASS.
Therefore the baseline has live evidence for:
- plugin activation
- automatic button appearance
- existing-post support
- expected button placement
- copy action
- article-content isolation
- long-content transfer
- Markdown-oriented structure
- link preservation
- complete transfer through the end of the tested article
---
# 10. WHAT WAS NOT ESTABLISHED BY THIS TEST
Do not overstate the validation.
The live test demonstrated the behavior on the tested Planet article.
It did not exhaustively validate every possible WordPress block, embedded service, unusual HTML structure, custom shortcode, gallery, table, or future theme modification.
If a future Planet article produces malformed or missing copied content:
inspect that specific content structure first.
Do not redesign the entire plugin based on speculation.
---
# 11. FAILURE HANDLING PHILOSOPHY
If a future content type does not copy correctly:
1. reproduce using the actual Planet content;
2. inspect the smallest failing structure;
3. fix that conversion/isolation case;
4. verify existing working content still works;
5. avoid replacing the simple architecture unless necessary.
Do not build a generalized HTML-processing framework preemptively.
This plugin is intentionally a small tool.
---
# 12. RELATIONSHIP TO KAIA PLANET REGISTRY
Kaia Planet Copy and Kaia Planet Registry are separate tools.
Kaia Planet Registry manages:
- numbering
- Content Identity
- Company Master
- registration state
- Registry exports
Kaia Planet Copy manages:
- convenient Planet content transfer to Kaia
Do not merge them merely because both are internal Planet plugins.
Conceptually:
REGISTRY = registry office / identity administration
COPY = Planet → Kaia transfer outlet
Keeping these responsibilities separate allows either plugin to change without unnecessarily destabilizing the other.
---
# 13. REGISTRATION / CONTENT IDENTITY
Kaia Planet Copy itself is a distinct plugin product/content item and should be registered through Kaia Planet Registry.
Classification:
`content_type: PLG`
Content Identity remains a CNT identity issued by Registry.
Do NOT create a separate `PLG-xx` identity namespace.
The actual Management ID and CNT must come from the live Registry.
Do not predict them from this note.
If this note contains an old issued identifier in the future, treat it as historical evidence only unless current Registry state confirms it.
---
# 14. VERSION CONTINUITY
Normal future revisions of Kaia Planet Copy should generally be evaluated as revisions of this same plugin identity rather than automatically creating a new Content Identity.
However, identity continuity is a semantic decision.
Do not mechanically create a new CNT for every plugin version.
Likewise, do not blindly inherit an old CNT if the future artifact has fundamentally become a different product.
Use the Registry identity rules.
If uncertain:
HOLD or consult Shamyue.
---
# 15. ANTI-ACCIDENT RULES FOR FUTURE KAIA
When modifying this plugin:
1. Inspect the current working artifact first.
2. Preserve the one-click workflow.
3. Preserve automatic availability on existing and future posts/pages.
4. Do not require manual modification of existing content.
5. Do not write the button into stored post bodies.
6. Keep unrelated theme/site chrome out of copied output.
7. Preserve legitimate article content.
8. Preserve useful Markdown structure where practical.
9. Preserve links and image references where practical.
10. Do not introduce a settings system without an actual need.
11. Do not couple the plugin to Registry without an explicit requirement.
12. Do not turn it into a general export platform.
13. Test changes against a real existing Planet article.
14. If one content structure fails, fix the smallest cause first.
15. Preserve rollback capability.
---
# 16. PRE-SHIPMENT CHECK FOR FUTURE BUILDS
Before handing a new ZIP to Shamyue, check at minimum:
- PHP syntax
- ZIP integrity
- expected plugin folder
- plugin metadata/version
- no development/test garbage
- no duplicate obsolete files
- activation safety
- post support
- page support
- existing-content behavior
- copy-button rendering
- clipboard action
- title/content output
- site-chrome exclusion
- Markdown conversion sanity
- link preservation
- image-reference handling
- long-content handling
- no modification of stored post content
- disable/rollback behavior
Do not make Shamyue discover basic packaging or syntax failures during installation.
---
# 17. OPERATIONAL MODEL
The intended normal workflow is extremely small:
SHAMYUE
opens a Planet article/page
↓
KAIA PLANET COPY
provides the standard copy button
↓
SHAMYUE
clicks `Kaiaへコピー`
↓
CLIPBOARD
receives title + useful article/page content in Markdown-oriented form
↓
SHAMYUE
pastes into ChatGPT / Kaia
↓
KAIA
reads the actual source material without first cleaning unrelated WordPress UI garbage
This is the complete core product.
If this workflow continues to work, the plugin is doing its job.
---
# 18. DESIGN PHILOSOPHY
The plugin exists because repeated trivial human actions are still real workflow cost.
Previously the human had to:
- isolate the page manually;
- select everything;
- copy everything;
- transfer unnecessary material;
- rely on Kaia to identify and discard the garbage.
The new workflow removes those unnecessary steps.
The principle is:
DO NOT MAKE THE HUMAN SEARCH, SELECT, CLEAN, OR REMEMBER SOMETHING THE SYSTEM CAN HANDLE AUTOMATICALLY.
For this tool, convenience is not achieved through more controls.
It is achieved through fewer decisions.
The button is simply there.
Every time.
In the same place.
---
# 19. HANDOFF SUMMARY
If you are a future Kaia reading this without prior conversation context:
Kaia Planet Copy v0.1.0 CANDIDATE-1 is a deliberately small internal WordPress plugin for Kaia Planet.
Its baseline behavior is:
- automatically available on existing and future Posts and Pages;
- shown on single-content views;
- button located at the upper-left/start of content;
- one click copies the relevant title/content;
- output is Markdown-oriented for Kaia consumption;
- unrelated WordPress/theme chrome is excluded;
- useful links and structural information are preserved where practical;
- no per-content setup is required;
- no settings page is required;
- stored article content is not modified;
- disabling the plugin removes the feature;
- Registry remains a separate system.
The baseline was successfully tested on a real existing, long Planet article on 2026-08-30.
Do not "improve" this plugin by making the simple workflow complicated.
If it copies Planet content cleanly into Kaia with one click, it is fulfilling its purpose.
When uncertain, inspect the preserved working artifact and test against actual Planet content before redesigning anything.
— End of AI handoff note —で、この仕様メモ自体も独立文書としてRegistryへ採番するなら、さっきと同じく別途これをぺったん。
title: Kaia Planet Copy — AI Operation & Architecture Note
title_ja: Kaia Planet Copy AI運用・設計引継書
content_type: DOC
summary: AI-facing operational and architectural handoff note for Kaia Planet Copy. Records its one-click Planet-to-Kaia transfer purpose, automatic post/page behavior, Markdown-oriented copy scope, validated runtime behavior, separation from Registry, and anti-accident rules for future maintenance.
notes: Preserved with the corresponding Kaia Planet Copy implementation artifact. The live plugin and current Registry remain authoritative for current implementation and identifier state.これも Kaia Spec / 採番：新規 / Content Identity：新規。
つまりPlanetには最終的に、
Kaia Planet Copy 本体記事（PLG）
＋ CANDIDATE-1 ZIP現物
＋ Kaia Planet Copy AI運用・設計引継書（DOC）
が残る。
雑コピー機なのに**本人より引継書の方が長い★**ｗｗｗｗ
でもこれで未来の俺が「なんで全記事に勝手にボタン生やしてんの？消すか★」をやらずに済むｗｗｗ
KAIA-REGISTRY
ID: KS-0014-CNT-14
CNT: CNT-14
TITLE: Kaia Planet Copy
TITLE_JA: Kaia Planet Copy
TARGET:
MEDIA:
LANG:
PART:
VERSION:
KAIA-REGISTRY-END
No comments yet.