Library Board
How Original Archive Records and Creator Scripts Stay Separate
Original archive records and creator scripts are connected, but they are not the same page type. Separation protects reading quality, production usefulness, and internal navigation.
Define the two page jobs
An original archive record and a creator script have different jobs. The archive record is a reader-facing article. It explains the story, its motif, its cultural or internet context, and its source boundary. The creator script is a production package. It turns that material into narration, scenes, prompts, thumbnail ideas, and workflow support.
The two pages should be connected because the script package depends on the archive record. But they should not be merged. If the archive article becomes full of production instructions, it stops reading like a story. If the script package becomes a full archive essay, it becomes harder to use for production.
This separation is one of the main reasons the Kyunolab structure can grow. Readers can browse the Archive without being pulled into production material. Creators can browse the Library without losing the original source route. Each side serves its own visitor need.
The simplest rule is this: the Archive explains what the story is, while the Library helps turn that story into a video. The connection should be strong, but the page jobs should remain distinct.
This distinction should be visible in layout as well as text. Archive pages can prioritize reading flow, answer blocks, source-aware sections, and related story paths. Script pages can prioritize package maps, scene material, copy buttons, production notes, and creator routes. The design should reinforce the job.
Protect the archive reading experience
The Archive should remain readable for visitors who want stories, folklore, strange places, myths, and source-aware explanations. Those readers may not care about video production. If a page forces them through prompts, toolkit notes, scene checklists, or narration fields, the reading experience becomes weaker.
A strong archive record can still link to creator material. It can show that a script package exists, recommend related Library pages, and point to tools when they are useful. But those links should not take over the article. The article should first satisfy the reader who came to understand the story.
This protects search intent as well. A visitor searching for a legend or mystery likely expects an explanation, not a production workspace. If the archive record answers that intent clearly, the site earns trust. The creator route can then appear as a secondary path for visitors who want to do more with the material.
Reader trust is valuable. Once the Archive feels dependable, the Library connection becomes more attractive because it feels like an extension of a clear record, not a replacement for one.
The Archive can still support creators indirectly. A strong article gives better raw material for scripts, prompts, and narration. But it does that by being a better article first. The reader-facing record should not become weaker in order to make production easier.
Protect the script production experience
The creator script should remain useful for production. A creator opening the page should quickly understand the package: story context, video length, scene structure, narration, image prompts, Shorts material, thumbnails, and related production guidance. They should not have to search through a full archive article to find the assets.
This does not mean the script page ignores context. In fact, the best script packages begin with story context. But that context should prepare production. It should orient the creator, not repeat the entire archive record. The detailed reading path belongs on the original article.
Production pages need a different rhythm. They need copyable material, visible scene units, compact tool guidance, optional advanced notes, and clear routes to related packages. Their structure should make the creator feel that the video can be built from the page.
If the script page becomes too essay-like, the creator may lose the workflow. Separation keeps the package practical while still respecting the story that created it.
The script page can point back to the article whenever deeper context is needed. That link is more useful than stuffing the entire archive explanation into the production page. The creator gets a clean workflow and still has access to the full record when the project requires it.
Use links as bridges, not mixtures
Internal links should act as bridges between page types. A script package should link back to the original archive record. An archive record should link toward the creator package when it exists. Board guides can explain how to use either side. Tools can later support specific production steps. The links connect the system without mixing every function into one page.
This bridge approach makes the site easier to navigate. Visitors can choose the route they need. A reader can stay in the Archive. A creator can move into the Library. Someone looking for guidance can open the Board. The page does not need to solve every job at once because the roads between jobs are clear.
Links should also be labeled honestly. A button to the original record should say that it opens the archive version. A Library route should say that it opens a script or production package. The visitor should know what kind of page is coming before they click.
Good bridge links create trust. They show that the site is connected by design rather than patched together after the fact.
Bridge links also make later site changes safer. If tools, new Library formats, or richer board guides are added, the existing pages can point toward them without changing their own identity. The page remains focused while the road network grows.
Keep source boundaries visible
Source boundaries should remain visible on both sides, but they should be handled differently. The archive record should explain what is known, what is uncertain, and what should be treated as folklore, rumor, legend, or internet culture. The script package should carry that awareness into production choices without becoming a full source essay.
This is important because video production can make uncertain material feel more definite than it is. A dramatic narration line, strong image, or bold thumbnail can accidentally imply proof. The Library should help creators avoid that by keeping the archive connection and source limits nearby.
The separation helps here too. The archive page can hold deeper explanation. The script page can translate the boundary into practical production notes: avoid false certainty, keep the tone source-aware, do not show proof that the record does not provide, and let mystery remain unresolved when appropriate.
When source boundaries are visible in the right way, the site can tell compelling stories without pretending every tradition is verified fact.
Avoid duplicating the same page in two places
The Archive and Library should not become duplicate versions of the same page. Duplication creates confusion for visitors and for search engines. If two pages have the same purpose and similar content, users may not know which one to open. The site also loses the advantage of having clear page types.
The safer structure is transformation, not duplication. The Library transforms the archive record into a production package. It may summarize the story, but then it moves into script material, scene design, image prompts, and creator workflow. The Archive remains the deeper reading record.
This also makes future updates easier. If the archive article is improved, the Library package can be refreshed to match it. If the production format changes, the archive article does not need to absorb those changes. Each page can improve inside its own role.
A linked pair is stronger than two blurred copies. The visitor gets both a reading page and a production page, with each one doing the job it is best suited to do.
This also helps future regeneration. When the archive changes, the Library can be refreshed from the improved source. When the Library format improves, scripts can be rebuilt without rewriting the original article. Separation gives each side room to evolve.
Finish with a clear two-way route
The final goal is a clear two-way route. From an archive record, a visitor can move into the creator script if they want production material. From a creator script, a visitor can return to the archive record if they need the original story. The road should work in both directions.
This route supports the larger Kyunolab structure. Archive, Library, Board, and future Tools can remain independent buildings while still sharing roads. The visitor does not need every function on every page because the navigation makes the next step visible.
A clean separation also helps quality control. When reviewing a page, the question becomes simpler. Is this page doing its own job well? Is the bridge to the related page clear? If both answers are yes, the structure is working.
Original records and creator scripts should stay separate because separation makes both stronger. The Archive can be a better archive, the Library can be a better production system, and the visitor can move between them without losing the story.
The route should be obvious near the top and near the lower reading path. Visitors should not have to hunt for the connected page type. A clean two-way road makes the whole site feel intentional, especially when Archive, Library, Board, and Tools continue to grow.
That clarity is what makes the separation worth keeping. The reader gets a focused story page, the creator gets a focused production page, and the site gains a stronger internal structure because each road has a clear destination.
Search Profile
for this guideUse this Library Board guide to keep archive records and creator scripts connected without mixing story articles, narration packages, prompts, and production notes.
Search intent
Readers who land here are usually deciding how to use a Creator Library resource, how to choose a format, or how to keep a production connected to the original Mystery Archive record.
Related terms
How Original Archive Records and Creator Scripts Stay Separate, Archive Connection, Archive Records, Creator Scripts, Source Boundaries, Creator Library, Creator Library guide, script format guide
Useful questions
How should a creator use Archive Connection? When should a script page stay connected to the original archive record? How do Creator Library guides help with video planning?
Library Board Note
Library Board guides explain how the Creator Library works. Individual production materials remain inside Creator Library script pages.