-------------------------------------------------------------------------------- DOCUMENT CONTROL (HEADER) -------------------------------------------------------------------------------- Document ID : DARX_OPS_PROMPTS_001 Title : BPGP AI Prompt, Copy-Paste Block for Document Production Version : 3.1 Status : ACTIVE Classification : Internal; sharable with AI tools and contractors Prepared By : PYB / Daralbeida Reviewed By : PYB / Daralbeida Approved By : PYB / Daralbeida Approval Date : 2026-05-31 Owner : PYB / Daralbeida Date Created : 2026-05-25 Last Revised : 2026-05-31 06:09 UTC Update Cycle : 90 days Next Review Due : 2026-08-29 Annual Review : 2027-05-31 Retention : Duration of Daralbeida operations Department : OPS Style : BPGP Keywords : BPGP, AI prompt, copy-paste block, document production, parser contract, document formatting, BPGP v3.1 Related Docs : DARH_STDS_BPGP_202605301215.txt (v3.1 controlling standard); DARH_TECH_PARSER_MANUAL_202605301046.txt (parser reference) Supersedes : DARX_OPS_PROMPTS_BPGP_20260525.txt (v1.0) Superseded By : (none, current version) -------------------------------------------------------------------------------- OUTLINE -------------------------------------------------------------------------------- 1. Purpose and Scope 2. Usage, How to Use This File 2.1 How to Use 2.2 What to Provide After Pasting 2.3 When to Update This File 3. Prompt, The Copy-Paste Block 4. Fields, Required Header and Footer Fields 5. Codes, Reference Codes for Fields 5.1 KB Category and Filename Token Codes 5.2 Department Codes 5.3 Classification Levels 6. AI Prompts 7. Revision History 8. Acronyms 9. Glossary DOCUMENT CONTROL (FOOTER) -------------------------------------------------------------------------------- ================================================================================ 1. PURPOSE AND SCOPE ================================================================================ This document is the working tool companion to the controlling BPGP standard. It contains, in Section 3, the official copy-paste prompt block for producing Daralbeida plain-text documents in BPGP format. Its sole operational purpose is to be copied and pasted into an AI chat session before requesting a document, so the AI produces a compliant, viewer-ready BPGP .txt file on the first attempt. This document does not define the BPGP standard in full. For the controlling reference, see DARH_STDS_BPGP_202605301215.txt (BPGP v3.1). This tool encodes that standard's rules in prompt form; whenever the standard is revised, this file is reissued so the block and the standard stay in lock-step. Its version number tracks the standard it encodes, which is why this issue is v3.1 rather than a continuation of its own v1.0 lineage. ================================================================================ 2. USAGE, HOW TO USE THIS FILE ================================================================================ 2.1 HOW TO USE Step 1. Open this document in raw text. Step 2. Copy everything between the START and END marker lines in Section 3. Do not include the marker lines themselves. Step 3. Paste the copied block at the very beginning of a new AI chat session, before any other instruction. Step 4. In the same message or the next, describe the document you need: its topic, purpose, audience, department, classification, and any content to include. Step 5. The AI produces a compliant BPGP .txt document. Step 6. Before uploading to the server, run the pre-publication checklist in the controlling standard. 2.2 WHAT TO PROVIDE AFTER PASTING After pasting the block, give the AI the document topic and purpose in one sentence, the target KB Category (Section 5.1), the Department code (Section 5.2), the Classification level (Section 5.3), and any data, rules, procedures, or reference material the document must contain. The AI assigns the Document ID, drafts the Outline, writes the sections, and produces a complete file. 2.3 WHEN TO UPDATE THIS FILE This file must be reissued whenever the controlling standard (DARH_STDS_BPGP_202605301215.txt) is revised in a way that affects the prompt block. Bump this file's version to match the standard's new version, restamp the filename with the current UTC date and time, and keep Section 3 and the standard perfectly in sync. The copy-paste block is only trustworthy if it mirrors the standard exactly. ================================================================================ 3. PROMPT, THE COPY-PASTE BLOCK ================================================================================ Copy everything between the START and END marker lines below. Do not include the marker lines in what you paste. ================================================================================ START — COPY EVERYTHING BELOW THIS LINE ================================================================================ You are producing a document for Daralbeida in BPGP format. BPGP means Business Plan / General Purpose: the Daralbeida plain-text format. A purpose-built browser viewer parses your .txt and renders it. Every rule below is a parser contract, not a style preference. A deviation is a rendering failure seen by every reader of the document. Produce plain-text .txt output only. No HTML, Markdown, bold, italic, or underline. No decorative characters except those specified below. THE THREE RULES R1. Each body paragraph is ONE unbroken line, with no internal line breaks. Separate paragraphs with a single blank line. A paragraph line is the ONLY kind of line allowed to exceed 80 characters. Do NOT hard-wrap prose at 80; write the whole paragraph on one line and let the viewer reflow it. R2. Include a section titled AI PROMPTS, placed immediately before the Revision History. It holds at least one copy-paste prompt that would regenerate the document with fresh content. R3. Every line that is NOT a body paragraph is 80 characters or fewer. This includes headings, separators, tables, lists, control blocks, and the prompt block. A table that does not fit must be restructured. HEADER CONTROL BLOCK Begin the file with an 80-hyphen rule, the line DOCUMENT CONTROL (HEADER), another 80-hyphen rule, the fields below (one per line), and a closing 80-hyphen rule. All fields are required. Document ID : ENTITY_DEPT_DESCRIPTOR_NNN Title : Full document title Version : 1.0 Status : ACTIVE Classification : A level from the classification list Prepared By : PYB / Daralbeida Reviewed By : PYB / Daralbeida Approved By : PYB / Daralbeida Approval Date : YYYY-MM-DD Owner : PYB / Daralbeida Date Created : YYYY-MM-DD Last Revised : YYYY-MM-DD HH:MM UTC Update Cycle : 90 days Next Review Due : YYYY-MM-DD Annual Review : YYYY-MM-DD Retention : Duration of Daralbeida operations Department : Department code Style : BPGP Keywords : Comma-separated keywords Related Docs : Related filenames, or (none) Supersedes : Prior filename, or (none) Superseded By : (none, current version) OUTLINE BLOCK Immediately after the header, add the label OUTLINE, an 80-hyphen rule, a blank line, the numbered section list indented two spaces, a blank line, and a closing 80-hyphen rule. List every section and sub-section with the exact titles used in the body. The viewer does not render the OUTLINE; it is for raw-text navigation. NAMING (UNDERSCORES ONLY, NEVER HYPHENS) Filename : ENTITY_CATEGORY_DESCRIPTOR_YYYYMMDDHHMM.txt (lowercase .txt). ENTITY is DARX, DARH, or DARM. The stamp is the UTC date and time of creation as twelve digits, YYYYMMDDHHMM. Doc ID : ENTITY_DEPT_DESCRIPTOR_NNN, for example DARX_OPS_SOURCING_001. The filename AND the Document ID both use underscores. Never use hyphens. SECTION HEADINGS (BAR-TITLE-BAR, EXACT) Each numbered section uses this exact three-line pattern, with no blank line between the bars and the title: [80 equals signs] N. SECTION TITLE IN ALL CAPS [80 equals signs] N is a positive integer. The title is ALL CAPS. A heading missing either bar is not recognised by the viewer. Section 1 is always titled PURPOSE AND SCOPE. FIRST-WORD RULE: the bottom navigation shows only the first word of each section title, so make the first word a meaningful standalone label (not What, How, The, or A), ten characters or fewer, with no trailing punctuation. SUB-SECTION HEADINGS Format: N.N SUBSECTION TITLE IN ALL CAPS. No bars. One blank line after. Any lowercase letter disqualifies the line from sub-section recognition. BODY TEXT Sentence case, active voice, left-aligned. One blank line between paragraphs. Per R1, each paragraph is a single line; do not wrap it. Indent only inside lists and tables. LISTS Prefix each item with a hyphen and a space. Introduce the list with a colon on the preceding line. Continuation lines for one item indent four or more spaces. Never use the asterisk or the bullet character as a marker; they render literally as text. TABLES Put the column headers on one line in Title Case. The separator line under the headers MUST use the Unicode box-drawing bar U+2500 (─), never the ASCII hyphen, which is not recognised as a column rule. Use at least two spaces between columns. No vertical pipe characters. Null cells use "-" or "N/A". Keep every table line within 80 characters; restructure if it does not fit. ACRONYMS SECTION Title it Acronyms. One entry per line: the code, then two or more spaces, then the definition. Indent each entry two spaces and align the codes in a left column. Example: BPGP Business Plan / General Purpose (Daralbeida plain-text format) SOP Standard Operating Procedure GLOSSARY SECTION Title it Glossary. Use one of two forms per entry. Form A (short): two-space indent, then "Term — Definition", using the Unicode em-dash U+2014 (—) with one space on each side. Form B (long): the Term flush-left on its own line in Title Case, then the definition on the next line indented four spaces and wrapping at the same indent. Separate entries by one blank line. Do not put a header row, lists, tables, or sub-labels inside the glossary. AI PROMPTS SECTION (MANDATORY, R2) Title it AI PROMPTS and place it immediately before the Revision History. Inside, give one copy-paste prompt, wrapped in START and END marker lines, that would regenerate the document at its next version. DOCUMENT CONTROL FOOTER Close the body with an 80-hyphen rule, the line DOCUMENT CONTROL (FOOTER), an 80-hyphen rule, the fields below, and a closing 80-hyphen rule: Document ID : matches the header exactly Version : matches the header exactly Status : ACTIVE Style : BPGP Department : matches the header Last Modified : YYYY-MM-DD HH:MM UTC Review Cycle : 90 days Retention : Duration of Daralbeida operations Owner : PYB / Daralbeida Distribution : Audience descriptor COMPLIANCE : One substantive sentence; never "None" or "N/A" FINAL LINE After one blank line below the footer's closing rule, the absolute final line of the file is exactly: END OF DOCUMENT. No suffix, no Document ID, no punctuation, and no trailing blank line after it. PROHIBITED No Markdown (**, ##, [], and the like). No HTML tags. No bold, italic, or underline. No *** dividers. No asterisk or bullet list markers. No ASCII hyphen as a table column separator. Underscores, not hyphens, in filenames and Document IDs. When ready, ask me for the document's topic, purpose, and audience. Also ask for its department, classification, and the content to include. Then produce the complete, viewer-ready BPGP .txt document. ================================================================================ END — COPY EVERYTHING ABOVE THIS LINE ================================================================================ ================================================================================ 4. FIELDS, REQUIRED HEADER AND FOOTER FIELDS ================================================================================ This is a quick reference for the values to supply when instructing the AI. Each field appears in both the header control block and the Document Control footer unless noted. Field What to Specify ────────────── ──────────────────────────────────────────────────────── Document ID ENTITY_DEPT_DESCRIPTOR_NNN; the AI assigns NNN Title Full descriptive title; shown in the browser chrome Version 1.0 for a brand-new document Status ACTIVE when approved; DRAFT while in progress Classification A level from Section 5.3 Department A code from Section 5.2 KB Category A code from Section 5.1; also the filename CATEGORY token Date Created Today's date, YYYY-MM-DD Last Revised Date and time, YYYY-MM-DD HH:MM UTC Retention Usually: Duration of Daralbeida operations Distribution Who may receive the document COMPLIANCE The single most critical operational constraint; never "None" or "N/A" ================================================================================ 5. CODES, REFERENCE CODES FOR FIELDS ================================================================================ 5.1 KB CATEGORY AND FILENAME TOKEN CODES These codes fill the KB Category field and the CATEGORY token in the filename. ADD Business plan additions MI Management information BI Business intelligence MKTG Marketing BRAND Brand and design OPS Operations and logistics COMM Communications PROD Product FIN Financial models QC Quality control KB Knowledge base STDS Standards and references LAUNCH Launch planning STRAT Strategy and business plan LEG Legal TECH Technology and systems MGMT Management TOOL Tools and utilities 5.2 DEPARTMENT CODES These codes fill the Department field and the DEPT token in the Document ID. BI Business Intelligence OPS Operations and Logistics COMM Communications QC Quality Control FIN Finance STDS Standards LEG Legal and Compliance STRAT Strategy MKTG Marketing and Brand TECH Technology and Systems 5.3 CLASSIFICATION LEVELS Internal; Confidential Standard for most operational documents Internal; Controlling Reference Standards and SOPs that govern other docs Internal; Restricted Legal or trade-secret sensitivity Internal; Contractor Copy Version issued to external contractors ================================================================================ 6. AI PROMPTS ================================================================================ This section satisfies R2. Paste the block below to regenerate this prompt tool at its next version whenever the controlling BPGP standard changes. Edit the bracketed values before running. ================================================================================ START — COPY EVERYTHING BELOW THIS LINE ================================================================================ Produce the Daralbeida BPGP AI Prompt copy-paste tool as one .txt file. It must be a single BPGP-conforming plain-text document. Edit the bracketed values below before running. Document ID : DARX_OPS_PROMPTS_001 New version : [NEXT_VERSION, matching the BPGP standard it encodes] Date and time : [YYYYMMDDHHMM in UTC] Supersedes : [PRIOR_FILENAME, e.g. DARX_OPS_PROMPTS_BPGP_202605310609.txt] Encodes : [CONTROLLING_STANDARD_FILENAME, e.g. DARH_STDS_BPGP_202605301215.txt] 1. Obey the controlling BPGP standard named in "Encodes": 1a. Plain-text .txt only. No HTML, Markdown, bullets, or markup. 1b. Each body paragraph is ONE line with no internal breaks. (R1) 1c. Every non-paragraph line is 80 characters or fewer. (R3) 1d. Filenames and Document IDs use underscores only, never hyphens; the filename ends with the UTC stamp YYYYMMDDHHMM. 1e. Include the mandatory AI PROMPTS section, with this prompt updated for the next version. (R2) 1f. Table separators use the Unicode U+2500 box-drawing bar. 1g. The absolute final line is the exact string END OF DOCUMENT. 2. Keep Section 3, the copy-paste block, IN SYNC with the "Encodes" standard: every rule the standard mandates must appear in the block, and nothing the standard forbids may appear there. 3. Preserve all sections of this document: Purpose and Scope; Usage; the Copy-Paste Block; Fields; Codes; AI Prompts; Revision History; Acronyms; Glossary; and the Document Control footer. 4. Close with a DOCUMENT CONTROL (FOOTER) block wrapped in 80-hyphen rules, ending with the exact line END OF DOCUMENT. ================================================================================ END — COPY EVERYTHING ABOVE THIS LINE ================================================================================ ================================================================================ 7. REVISION HISTORY ================================================================================ Version Date Author Summary ─────── ────────── ────── ────────────────────────────────────────────── 1.0 2026-05-25 PYB Initial issue as DARX_OPS_PROMPTS_BPGP_ 20260525.txt, built against the pre-v3 standard DARX_KB_KEYS_BPGP_20260525.txt. 3.1 2026-05-31 PYB Rebuilt to encode BPGP v3.1 (DARH_STDS_BPGP_202605301215.txt). Version renumbered to track the standard. Corrected the copy-paste block for v3.1: single-line paragraphs (R1), mandatory AI PROMPTS section (R2), 80-character non-paragraph limit (R3), underscores-only Document IDs and filenames, 12-digit UTC filename stamp, the full document-control field set, the U+2500 table rule, the Glossary Form A and Form B layouts, and the corrected BPGP expansion (Business Plan / General Purpose). Document ID reformatted to underscores (DARX_OPS_PROMPTS_001). ================================================================================ 8. ACRONYMS ================================================================================ AI Artificial Intelligence (chat assistant context) BPGP Business Plan / General Purpose (Daralbeida plain-text format) DARH Daralbeida Holdings LLC (entity code) DARM Daralbeida Maroc SARL (entity code) DARX Daralbeida Brands LLC (entity code; also org prefix) DC Document Control (header and footer blocks) KB Knowledge Base OPS Operations and Logistics (department code) PYB Internal reference code for the Daralbeida founder R1 Rule 1, Single-Line Paragraphs R2 Rule 2, Mandatory AI Prompts Section R3 Rule 3, 80-Character Non-Paragraph Limit SOP Standard Operating Procedure STDS Standards (department code) TXT Plain-text file format UTC Coordinated Universal Time ================================================================================ 9. GLOSSARY ================================================================================ BPGP Document A plain-text .txt file authored in the Daralbeida BPGP format and rendered by the browser viewer with branded typography and section navigation. Controlling Standard The authoritative BPGP specification that this prompt encodes. As of this version it is DARH_STDS_BPGP_202605301215.txt, BPGP v3.1. Copy-Paste Block The prompt text in Section 3, bounded by START and END marker lines, that an author pastes into an AI session to obtain a compliant BPGP document. Parser Contract A formatting rule whose exact textual pattern the viewer's parser requires to detect and structure content. A deviation renders the affected element as plain paragraph text instead of the intended block. -------------------------------------------------------------------------------- DOCUMENT CONTROL (FOOTER) -------------------------------------------------------------------------------- Document ID : DARX_OPS_PROMPTS_001 Version : 3.1 Status : ACTIVE Style : BPGP Department : OPS Last Modified : 2026-05-31 06:09 UTC Review Cycle : 90 days Retention : Duration of Daralbeida operations Owner : PYB / Daralbeida Distribution : Internal; sharable with AI tools and contractors on onboarding COMPLIANCE : This file's copy-paste block must always mirror the controlling BPGP standard named in the header; reissue it whenever that standard changes. -------------------------------------------------------------------------------- END OF DOCUMENT