playbook:sop:document_formatting [Chenla Wiki

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.
====== SOP-05: Document Formatting & Hierarchy ======

This SOP defines the standard structure, hierarchy, and formatting rules for all Chenla Agathos Solutions documents. Its purpose is to ensure clarity, consistency, and professional presentation across teams and project types.

===== 1. Scope =====
This SOP applies to:
  * Reports, proposals, and questionnaires
  * Engineering and technical documentation
  * Internal strategy documents
  * Templates and standardized forms

===== 2. Document Structure =====

==== 2.1 Title Block ====
  * Use H1 (24pt, SemiBold) for primary titles.
  * Titles must be left-aligned unless the document template specifies otherwise.
  * Underlines match text width and use thin, consistent rule weights.
  * Do not use shaded boxes, decorative borders, or centered title blocks unless part of a designated template.

==== 2.2 Section Hierarchy ====
  * **H1:** Reserved for document title only.
  * **H2:** Section headings (16pt, Bold).
  * **H3:** Subsections (13pt, SemiBold).
  * All headings follow a single alignment grid and consistent vertical spacing.
  * Avoid skipping levels (e.g., do not jump from H1 directly to H3).

==== 2.3 Body Text ====
  * Default body text: IBM Plex Sans, 11pt, Regular, line-height 1.35.
  * Paragraph spacing: 4–8pt depending on context.
  * Lists use hyphens or numbered markers; avoid decorative bullets.
  * Avoid italics for extended body text.

==== 2.4 Notes & Callouts ====
Use the standardized left-rule callout format:

<code>
│ This is a note, instruction, or clarification.
│ Use callouts for guidance rather than core content.
</code>

  * Keep tone instructional and neutral.
  * No shading or background color unless specified.

===== 3. Alignment & Spacing =====
  * All documents use a strong left margin anchor for text and lists.
  * Maintain consistent spacing increments between headings, paragraphs, and lists.
  * Avoid multiple visual centers on the same page.
  * Use generous negative space to maintain clarity.

===== 4. Tables & Forms =====
  * Use simple, thin rules.
  * Avoid heavy borders or dense shading.
  * Form fields use single, consistent underline lengths.
  * Checkbox size: 9–10pt; align checkboxes with text baselines.

===== 5. Images & Logos =====
  * Align with the left margin unless otherwise specified.
  * Maintain consistent scaling relative to text size.
  * Never stretch, distort, or apply effects.

===== 6. Review & Compliance =====
All new templates and document formats must be reviewed for:
  * Alignment with Chenla brand identity
  * Typography consistency
  * Proper use of spacing and hierarchy
  * Footer structure (per SOP-06)

---

====== SOP-06: Collaboration Branding & Footer Workflow ======

This SOP defines how Chenla Agathos Solutions presents its identity in collaborative documents and establishes a consistent footer system for technical and client-facing deliverables.

===== 1. Scope =====
This SOP applies to:
  * Joint documents with partner firms
  * Client-facing questionnaires, briefs, and reports
  * Any materials requiring shared authorship presentation
  * All documents using Chenla’s standardized footer

===== 2. Collaboration Branding =====

==== 2.1 Collaboration Mark ====
Use a neutral, typographic collaboration mark when multiple organizations appear on the same document:
  * Format: `PARTNER × CHENLA`
  * Typeface: Monospace or technical sans
  * Case: ALL CAPS
  * Slight positive letterspacing for clarity

==== 2.2 When to Use Full Logos ====
Full logos may be used when:
  * Required by contractual or presentation standards
  * Used on cover pages or formal joint submissions
  * Representing dual authorship in a visually balanced layout

Logos must be scaled to *optical* equality:
  * Increase delicate logos slightly
  * Decrease heavier logos slightly
  * Align along a shared baseline

==== 2.3 Forbidden Uses ====
Logos may not:
  * Appear inside decorative containers
  * Be recolored outside approved palettes
  * Compete for dominance in the header
  * Be used without adequate negative space

===== 3. Footer Standards =====

==== 3.1 Required Elements ====
Each Chenla document footer contains:
  * **Left:** Revision number and document number  
  * **Center:** Micro-mark or internal identifier  
  * **Right:** Page numbering  
  * Optional: Confidentiality notice (light green)

==== 3.2 Revision System ====
  * **Rev 0.x:** Drafts
  * **Rev 1.0:** First issued version
  * Include issue date with every revision update

==== 3.3 Document Number Format ====
Standard pattern:
  * `CAS-{Partner}-{DocumentType}-{Index}`
Example:
  * `CAS-BLOOM-DSR-001`

===== 4. Footer Formatting =====
  * Typeface: IBM Plex Sans or IBM Plex Mono
  * Left block uses Regular weight; confidentiality line in light green
  * Micro-mark centered vertically and horizontally within footer block
  * Page numbers right-aligned to inner frame margin
  * Maintain consistent footer height across all pages and templates

===== 5. Workflow for Creating Collaborative Documents =====
  * Begin with approved Chenla template.
  * Insert partner logo or collaboration mark according to optical balance rules.
  * Apply standardized typographic hierarchy (SOP-05).
  * Insert footer elements using the revision and document numbering format.
  * Verify alignment against Chenla’s layout grid.
  * Export only to PDF for client-facing materials unless otherwise required.

===== 6. Review & Compliance =====
  * All new collaborative templates must be reviewed by the branding lead.
  * All external documents must use the standardized footer.
  * Deviations require explicit approval.