@ryanyahya/opendoc 0.4.0

package/starter/templates/company-profile/preview.tsx

@@ -0,0 +1,185 @@
+import { CompanyProfile, ProfileSlide, ProfileRegion, ProfileText, ProfileImage, ProfileRule, ProfileRow } from './index';
+import { neutral as theme } from '../../themes';
+
+const title = 'Company profile';
+const themeId = 'neutral';
+export const meta = { title, description: 'A company profile with replaceable content and image positions.', kind: 'company profile', theme: themeId };
+
+
+// This content belongs to the instance. Replace placeholders with supplied facts.
+// Remove irrelevant slides, keep IDs stable, and add slides rather than squeezing copy.
+// Image example: image={{item:'team-at-work',position:{x:0.6,y:0.5}}}
+export default function Specimen() {
+  return <CompanyProfile title={title} theme={theme}>
+    <ProfileSlide id="profile-cover" theme={theme} cover title={title} eyebrow="COMPANY PROFILE / [EDITION DATE]" folio="01">
+      <ProfileImage id="cover-image" theme={theme} x={560} y={0} width={400} height={540} label="Signature project or place" />
+      <ProfileRegion x={40} y={364} width={450} height={104}>
+        <ProfileText id="cover-positioning" theme={theme} size={23}>[Company name] helps [audience] achieve [specific outcome].</ProfileText>
+        <ProfileText id="cover-context" theme={theme} size={13} muted>[Prepared for audience / geography / edition]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-snapshot" theme={theme} title="The company at a glance." eyebrow="01 / INTRODUCTION" folio="02">
+      <ProfileRegion x={40} y={196} width={428} height={266}>
+        <ProfileText id="snapshot-positioning" theme={theme} size={29}>[What you do, for whom, and the useful difference you make.]</ProfileText>
+        <ProfileText id="snapshot-description" theme={theme} size={18} muted>[Explain the business in plain language. State the actual scale and scope; distinguish the company from a group or partner network.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={510} y={202} width={410} />
+      <ProfileRegion x={530} y={216} width={175} height={108}>
+        <ProfileText id="snapshot-founded-label" theme={theme} size={12} label>ESTABLISHED</ProfileText>
+        <ProfileText id="snapshot-founded" theme={theme} size={27}>[Year]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={740} y={216} width={180} height={108}>
+        <ProfileText id="snapshot-base-label" theme={theme} size={12} label>BASED IN</ProfileText>
+        <ProfileText id="snapshot-base" theme={theme} size={27}>[Location]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={510} y={338} width={410} />
+      <ProfileRegion x={530} y={354} width={175} height={116}>
+        <ProfileText id="snapshot-team-label" theme={theme} size={12} label>TEAM / CAPACITY</ProfileText>
+        <ProfileText id="snapshot-team" theme={theme} size={22}>[Verified figure]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={740} y={354} width={180} height={116}>
+        <ProfileText id="snapshot-status-label" theme={theme} size={12} label>OWNERSHIP / STATUS</ProfileText>
+        <ProfileText id="snapshot-status" theme={theme} size={22}>[Accurate status]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-purpose" theme={theme} title="The belief behind the work." eyebrow="02 / POINT OF VIEW" folio="03">
+      <ProfileRegion x={40} y={204} width={585} height={210}>
+        <ProfileText id="purpose-statement" theme={theme} size={39}>[A clear point of view about what should improve in your field.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={680} y={204} width={240} height={256}>
+        <ProfileText id="purpose-practice-label" theme={theme} size={12} label>IN PRACTICE</ProfileText>
+        <ProfileText id="purpose-practice" theme={theme} size={20}>[Describe the decision or behavior this belief changes. Show a useful principle instead of a list of generic values.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={40} y={444} width={585} />
+      <ProfileRegion x={40} y={456} width={585} height={26}><ProfileText id="purpose-proof" theme={theme} size={12} muted>[One practical example, documented policy, or relevant commitment.]</ProfileText></ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-capabilities" theme={theme} title="What we bring to the table." eyebrow="03 / CAPABILITIES" folio="04">
+      <ProfileRegion x={40} y={196} width={880} height={282}>
+        <ProfileRow id="capability-discovery" theme={theme} number="01" title="[Core capability]" detail="[Name the buyer's need and the concrete deliverable you provide.]" />
+        <ProfileRow id="capability-delivery" theme={theme} number="02" title="[Core capability]" detail="[Describe a distinct service, product, or expertise. Avoid overlapping categories.]" />
+        <ProfileRow id="capability-support" theme={theme} number="03" title="[Core capability]" detail="[Explain the outcome and a specific differentiator you can substantiate.]" />
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-sectors" theme={theme} title="Where our expertise is relevant." eyebrow="04 / SECTORS & CONTEXTS" folio="05">
+      <ProfileImage id="sector-primary-image" theme={theme} x={40} y={192} width={510} height={236} label="Sector / product / operating context" />
+      <ProfileImage id="sector-secondary-image" theme={theme} x={574} y={192} width={346} height={106} label="Second context" />
+      <ProfileImage id="sector-detail-image" theme={theme} x={574} y={322} width={150} height={106} label="Detail" />
+      <ProfileRegion x={746} y={322} width={174} height={108}>
+        <ProfileText id="sector-detail" theme={theme} size={16}>[A specific use case that makes the sector relevant.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={40} y={443} width={510} height={40}><ProfileText id="sector-primary" theme={theme} size={17}>[Sector] / [typical need or application]</ProfileText></ProfileRegion>
+      <ProfileRegion x={574} y={443} width={346} height={40}><ProfileText id="sector-secondary" theme={theme} size={15} muted>[Additional verified sectors, if useful]</ProfileText></ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-method" theme={theme} title="How the work moves forward." eyebrow="05 / OPERATING MODEL" folio="06">
+      <ProfileRule theme={theme} x={40} y={216} width={880} />
+      <ProfileRegion x={40} y={232} width={202} height={236}>
+        <ProfileText id="method-align-number" theme={theme} size={34} muted>01</ProfileText>
+        <ProfileText id="method-align-title" theme={theme} size={24}>[Understand]</ProfileText>
+        <ProfileText id="method-align-detail" theme={theme} size={18}>[How needs, context, and success criteria become clear.]</ProfileText>
+        <ProfileText id="method-align-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={266} y={232} width={202} height={236}>
+        <ProfileText id="method-shape-number" theme={theme} size={34} muted>02</ProfileText>
+        <ProfileText id="method-shape-title" theme={theme} size={24}>[Shape]</ProfileText>
+        <ProfileText id="method-shape-detail" theme={theme} size={18}>[How options become an agreed approach with clear ownership.]</ProfileText>
+        <ProfileText id="method-shape-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={492} y={232} width={202} height={236}>
+        <ProfileText id="method-deliver-number" theme={theme} size={34} muted>03</ProfileText>
+        <ProfileText id="method-deliver-title" theme={theme} size={24}>[Deliver]</ProfileText>
+        <ProfileText id="method-deliver-detail" theme={theme} size={18}>[How work is produced, checked, and handed over.]</ProfileText>
+        <ProfileText id="method-deliver-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={718} y={232} width={202} height={236}>
+        <ProfileText id="method-improve-number" theme={theme} size={34} muted>04</ProfileText>
+        <ProfileText id="method-improve-title" theme={theme} size={24}>[Improve]</ProfileText>
+        <ProfileText id="method-improve-detail" theme={theme} size={18}>[How performance, learning, or ongoing support is handled.]</ProfileText>
+        <ProfileText id="method-improve-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-case-context" theme={theme} title="[A project that shows the work.]" eyebrow="06 / SELECTED WORK" folio="07">
+      <ProfileImage id="case-hero-image" theme={theme} x={40} y={196} width={580} height={280} label="Actual project / product / result" />
+      <ProfileRegion x={656} y={196} width={264} height={280}>
+        <ProfileText id="case-client-label" theme={theme} size={12} label>CLIENT / CONTEXT</ProfileText>
+        <ProfileText id="case-client" theme={theme} size={23}>[Named with permission, or accurately anonymized]</ProfileText>
+        <ProfileText id="case-role-label" theme={theme} size={12} label>OUR ROLE</ProfileText>
+        <ProfileText id="case-role" theme={theme} size={18}>[Specific scope. Distinguish your contribution from the wider project.]</ProfileText>
+        <ProfileText id="case-period" theme={theme} size={13} muted>[Location / delivery period / status]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-case-evidence" theme={theme} title="What changed, and how we know." eyebrow="06 / SELECTED WORK — EVIDENCE" folio="08">
+      <ProfileRegion x={40} y={200} width={264} height={210}>
+        <ProfileText id="case-challenge-label" theme={theme} size={12} label>THE CHALLENGE</ProfileText>
+        <ProfileText id="case-challenge" theme={theme} size={22}>[The starting situation and constraints that mattered.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={342} y={200} width={264} height={210}>
+        <ProfileText id="case-action-label" theme={theme} size={12} label>OUR CONTRIBUTION</ProfileText>
+        <ProfileText id="case-action" theme={theme} size={22}>[The concrete intervention and the part your team owned.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={644} y={200} width={276} height={210}>
+        <ProfileText id="case-outcome-label" theme={theme} size={12} label>THE OBSERVED RESULT</ProfileText>
+        <ProfileText id="case-outcome" theme={theme} size={28}>[Verified outcome]</ProfileText>
+        <ProfileText id="case-outcome-context" theme={theme} size={15} muted>[Unit, baseline, period, and qualification where needed.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={40} y={430} width={880} />
+      <ProfileRegion x={40} y={444} width={880} height={38}>
+        <ProfileText id="case-source" theme={theme} size={13} muted>Evidence / [Source, date, measurement method, permission, and limits of attribution.]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-footprint" theme={theme} title="Present where the work happens." eyebrow="07 / PRESENCE & REACH" folio="09">
+      <ProfileRegion x={40} y={200} width={400} height={276}>
+        <ProfileText id="footprint-base-label" theme={theme} size={12} label>OFFICE / OPERATING BASE</ProfileText>
+        <ProfileText id="footprint-base" theme={theme} size={26}>[Actual location]</ProfileText>
+        <ProfileText id="footprint-service-label" theme={theme} size={12} label>ACTIVE SERVICE AREA</ProfileText>
+        <ProfileText id="footprint-service" theme={theme} size={22}>[Locations you can currently serve]</ProfileText>
+        <ProfileText id="footprint-model" theme={theme} size={17} muted>[Explain local presence, remote delivery, or partner coverage accurately. Include relevant limits.]</ProfileText>
+      </ProfileRegion>
+      <ProfileImage id="footprint-image" theme={theme} x={486} y={196} width={434} height={234} label="Workplace / facility / local context" />
+      <ProfileRegion x={486} y={445} width={434} height={35}><ProfileText id="footprint-caption" theme={theme} size={13} muted>[Location and truthful caption; date if relevant]</ProfileText></ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-people" theme={theme} title="The people accountable for the work." eyebrow="08 / PEOPLE & EXPERTISE" folio="10">
+      <ProfileImage id="people-lead-image" theme={theme} x={40} y={196} width={266} height={164} label="Portrait / team at work" />
+      <ProfileImage id="people-delivery-image" theme={theme} x={346} y={196} width={266} height={164} label="Portrait / team at work" />
+      <ProfileImage id="people-specialist-image" theme={theme} x={652} y={196} width={268} height={164} label="Portrait / team at work" />
+      <ProfileRegion x={40} y={376} width={266} height={104}>
+        <ProfileText id="people-lead-name" theme={theme} size={22}>[Name / role]</ProfileText>
+        <ProfileText id="people-lead-expertise" theme={theme} size={16} muted>[Relevant expertise and what this person is accountable for.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={346} y={376} width={266} height={104}>
+        <ProfileText id="people-delivery-name" theme={theme} size={22}>[Name / role]</ProfileText>
+        <ProfileText id="people-delivery-expertise" theme={theme} size={16} muted>[Relevant expertise and what this person is accountable for.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={652} y={376} width={268} height={104}>
+        <ProfileText id="people-specialist-name" theme={theme} size={22}>[Name / role]</ProfileText>
+        <ProfileText id="people-specialist-expertise" theme={theme} size={16} muted>[Relevant expertise and what this person is accountable for.]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-assurance" theme={theme} title="The standards we can stand behind." eyebrow="09 / CREDENTIALS & RESPONSIBILITY — OPTIONAL" folio="11">
+      <ProfileRegion x={40} y={196} width={880} height={282}>
+        <ProfileRow id="assurance-credential" theme={theme} number="01" title="[Credential / license]" detail="[Issuer, exact scope, current status, expiry, and verification source. Omit if not applicable.]" />
+        <ProfileRow id="assurance-quality" theme={theme} number="02" title="[Quality / governance]" detail="[A real process or policy, its owner, and evidence of how it is applied.]" />
+        <ProfileRow id="assurance-responsibility" theme={theme} number="03" title="[Responsibility]" detail="[A documented commitment or measured result. Distinguish future goals from achieved outcomes.]" />
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-contact" theme={theme} cover title="Start a useful conversation." titleSize={48} eyebrow="10 / CONTACT" folio="12">
+      <ProfileImage id="contact-image" theme={theme} x={560} y={0} width={400} height={540} label="People / product / place" />
+      <ProfileRegion x={40} y={354} width={464} height={124}>
+        <ProfileText id="contact-name" theme={theme} size={21}>[Contact name / role]</ProfileText>
+        <ProfileText id="contact-email" theme={theme} size={18}>[Email] / [Phone]</ProfileText>
+        <ProfileText id="contact-website" theme={theme} size={18}>[Website] / [Office or time zone]</ProfileText>
+        <ProfileText id="contact-invitation" theme={theme} size={13} muted>[A clear reason to connect and the next conversation to have.]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+  </CompanyProfile>;
+}

package/starter/templates/company-profile/starter.tsx

@@ -0,0 +1,186 @@
+import { CompanyProfile, ProfileSlide, ProfileRegion, ProfileText, ProfileImage, ProfileRule, ProfileRow } from '../../templates/company-profile';
+// @ts-ignore The selected local theme module is inserted when this starter becomes a document.
+import { theme } from "__OPENDOC_THEME_MODULE__";
+
+const title = "__OPENDOC_TITLE__";
+const themeId = "__OPENDOC_THEME__";
+export const meta = { title, description: 'A company profile with replaceable content and image positions.', kind: 'company profile', theme: themeId };
+export const provenance = { template: 'templates/company-profile/index.tsx' };
+
+// This content belongs to the instance. Replace placeholders with supplied facts.
+// Remove irrelevant slides, keep IDs stable, and add slides rather than squeezing copy.
+// Image example: image={{item:'team-at-work',position:{x:0.6,y:0.5}}}
+export default function Profile() {
+  return <CompanyProfile title={title} theme={theme}>
+    <ProfileSlide id="profile-cover" theme={theme} cover title={title} eyebrow="COMPANY PROFILE / [EDITION DATE]" folio="01">
+      <ProfileImage id="cover-image" theme={theme} x={560} y={0} width={400} height={540} label="Signature project or place" />
+      <ProfileRegion x={40} y={364} width={450} height={104}>
+        <ProfileText id="cover-positioning" theme={theme} size={23}>[Company name] helps [audience] achieve [specific outcome].</ProfileText>
+        <ProfileText id="cover-context" theme={theme} size={13} muted>[Prepared for audience / geography / edition]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-snapshot" theme={theme} title="The company at a glance." eyebrow="01 / INTRODUCTION" folio="02">
+      <ProfileRegion x={40} y={196} width={428} height={266}>
+        <ProfileText id="snapshot-positioning" theme={theme} size={29}>[What you do, for whom, and the useful difference you make.]</ProfileText>
+        <ProfileText id="snapshot-description" theme={theme} size={18} muted>[Explain the business in plain language. State the actual scale and scope; distinguish the company from a group or partner network.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={510} y={202} width={410} />
+      <ProfileRegion x={530} y={216} width={175} height={108}>
+        <ProfileText id="snapshot-founded-label" theme={theme} size={12} label>ESTABLISHED</ProfileText>
+        <ProfileText id="snapshot-founded" theme={theme} size={27}>[Year]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={740} y={216} width={180} height={108}>
+        <ProfileText id="snapshot-base-label" theme={theme} size={12} label>BASED IN</ProfileText>
+        <ProfileText id="snapshot-base" theme={theme} size={27}>[Location]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={510} y={338} width={410} />
+      <ProfileRegion x={530} y={354} width={175} height={116}>
+        <ProfileText id="snapshot-team-label" theme={theme} size={12} label>TEAM / CAPACITY</ProfileText>
+        <ProfileText id="snapshot-team" theme={theme} size={22}>[Verified figure]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={740} y={354} width={180} height={116}>
+        <ProfileText id="snapshot-status-label" theme={theme} size={12} label>OWNERSHIP / STATUS</ProfileText>
+        <ProfileText id="snapshot-status" theme={theme} size={22}>[Accurate status]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-purpose" theme={theme} title="The belief behind the work." eyebrow="02 / POINT OF VIEW" folio="03">
+      <ProfileRegion x={40} y={204} width={585} height={210}>
+        <ProfileText id="purpose-statement" theme={theme} size={39}>[A clear point of view about what should improve in your field.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={680} y={204} width={240} height={256}>
+        <ProfileText id="purpose-practice-label" theme={theme} size={12} label>IN PRACTICE</ProfileText>
+        <ProfileText id="purpose-practice" theme={theme} size={20}>[Describe the decision or behavior this belief changes. Show a useful principle instead of a list of generic values.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={40} y={444} width={585} />
+      <ProfileRegion x={40} y={456} width={585} height={26}><ProfileText id="purpose-proof" theme={theme} size={12} muted>[One practical example, documented policy, or relevant commitment.]</ProfileText></ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-capabilities" theme={theme} title="What we bring to the table." eyebrow="03 / CAPABILITIES" folio="04">
+      <ProfileRegion x={40} y={196} width={880} height={282}>
+        <ProfileRow id="capability-discovery" theme={theme} number="01" title="[Core capability]" detail="[Name the buyer's need and the concrete deliverable you provide.]" />
+        <ProfileRow id="capability-delivery" theme={theme} number="02" title="[Core capability]" detail="[Describe a distinct service, product, or expertise. Avoid overlapping categories.]" />
+        <ProfileRow id="capability-support" theme={theme} number="03" title="[Core capability]" detail="[Explain the outcome and a specific differentiator you can substantiate.]" />
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-sectors" theme={theme} title="Where our expertise is relevant." eyebrow="04 / SECTORS & CONTEXTS" folio="05">
+      <ProfileImage id="sector-primary-image" theme={theme} x={40} y={192} width={510} height={236} label="Sector / product / operating context" />
+      <ProfileImage id="sector-secondary-image" theme={theme} x={574} y={192} width={346} height={106} label="Second context" />
+      <ProfileImage id="sector-detail-image" theme={theme} x={574} y={322} width={150} height={106} label="Detail" />
+      <ProfileRegion x={746} y={322} width={174} height={108}>
+        <ProfileText id="sector-detail" theme={theme} size={16}>[A specific use case that makes the sector relevant.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={40} y={443} width={510} height={40}><ProfileText id="sector-primary" theme={theme} size={17}>[Sector] / [typical need or application]</ProfileText></ProfileRegion>
+      <ProfileRegion x={574} y={443} width={346} height={40}><ProfileText id="sector-secondary" theme={theme} size={15} muted>[Additional verified sectors, if useful]</ProfileText></ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-method" theme={theme} title="How the work moves forward." eyebrow="05 / OPERATING MODEL" folio="06">
+      <ProfileRule theme={theme} x={40} y={216} width={880} />
+      <ProfileRegion x={40} y={232} width={202} height={236}>
+        <ProfileText id="method-align-number" theme={theme} size={34} muted>01</ProfileText>
+        <ProfileText id="method-align-title" theme={theme} size={24}>[Understand]</ProfileText>
+        <ProfileText id="method-align-detail" theme={theme} size={18}>[How needs, context, and success criteria become clear.]</ProfileText>
+        <ProfileText id="method-align-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={266} y={232} width={202} height={236}>
+        <ProfileText id="method-shape-number" theme={theme} size={34} muted>02</ProfileText>
+        <ProfileText id="method-shape-title" theme={theme} size={24}>[Shape]</ProfileText>
+        <ProfileText id="method-shape-detail" theme={theme} size={18}>[How options become an agreed approach with clear ownership.]</ProfileText>
+        <ProfileText id="method-shape-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={492} y={232} width={202} height={236}>
+        <ProfileText id="method-deliver-number" theme={theme} size={34} muted>03</ProfileText>
+        <ProfileText id="method-deliver-title" theme={theme} size={24}>[Deliver]</ProfileText>
+        <ProfileText id="method-deliver-detail" theme={theme} size={18}>[How work is produced, checked, and handed over.]</ProfileText>
+        <ProfileText id="method-deliver-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={718} y={232} width={202} height={236}>
+        <ProfileText id="method-improve-number" theme={theme} size={34} muted>04</ProfileText>
+        <ProfileText id="method-improve-title" theme={theme} size={24}>[Improve]</ProfileText>
+        <ProfileText id="method-improve-detail" theme={theme} size={18}>[How performance, learning, or ongoing support is handled.]</ProfileText>
+        <ProfileText id="method-improve-output" theme={theme} size={12} muted>OUTPUT / [Decision or artifact]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-case-context" theme={theme} title="[A project that shows the work.]" eyebrow="06 / SELECTED WORK" folio="07">
+      <ProfileImage id="case-hero-image" theme={theme} x={40} y={196} width={580} height={280} label="Actual project / product / result" />
+      <ProfileRegion x={656} y={196} width={264} height={280}>
+        <ProfileText id="case-client-label" theme={theme} size={12} label>CLIENT / CONTEXT</ProfileText>
+        <ProfileText id="case-client" theme={theme} size={23}>[Named with permission, or accurately anonymized]</ProfileText>
+        <ProfileText id="case-role-label" theme={theme} size={12} label>OUR ROLE</ProfileText>
+        <ProfileText id="case-role" theme={theme} size={18}>[Specific scope. Distinguish your contribution from the wider project.]</ProfileText>
+        <ProfileText id="case-period" theme={theme} size={13} muted>[Location / delivery period / status]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-case-evidence" theme={theme} title="What changed, and how we know." eyebrow="06 / SELECTED WORK — EVIDENCE" folio="08">
+      <ProfileRegion x={40} y={200} width={264} height={210}>
+        <ProfileText id="case-challenge-label" theme={theme} size={12} label>THE CHALLENGE</ProfileText>
+        <ProfileText id="case-challenge" theme={theme} size={22}>[The starting situation and constraints that mattered.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={342} y={200} width={264} height={210}>
+        <ProfileText id="case-action-label" theme={theme} size={12} label>OUR CONTRIBUTION</ProfileText>
+        <ProfileText id="case-action" theme={theme} size={22}>[The concrete intervention and the part your team owned.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={644} y={200} width={276} height={210}>
+        <ProfileText id="case-outcome-label" theme={theme} size={12} label>THE OBSERVED RESULT</ProfileText>
+        <ProfileText id="case-outcome" theme={theme} size={28}>[Verified outcome]</ProfileText>
+        <ProfileText id="case-outcome-context" theme={theme} size={15} muted>[Unit, baseline, period, and qualification where needed.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRule theme={theme} x={40} y={430} width={880} />
+      <ProfileRegion x={40} y={444} width={880} height={38}>
+        <ProfileText id="case-source" theme={theme} size={13} muted>Evidence / [Source, date, measurement method, permission, and limits of attribution.]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-footprint" theme={theme} title="Present where the work happens." eyebrow="07 / PRESENCE & REACH" folio="09">
+      <ProfileRegion x={40} y={200} width={400} height={276}>
+        <ProfileText id="footprint-base-label" theme={theme} size={12} label>OFFICE / OPERATING BASE</ProfileText>
+        <ProfileText id="footprint-base" theme={theme} size={26}>[Actual location]</ProfileText>
+        <ProfileText id="footprint-service-label" theme={theme} size={12} label>ACTIVE SERVICE AREA</ProfileText>
+        <ProfileText id="footprint-service" theme={theme} size={22}>[Locations you can currently serve]</ProfileText>
+        <ProfileText id="footprint-model" theme={theme} size={17} muted>[Explain local presence, remote delivery, or partner coverage accurately. Include relevant limits.]</ProfileText>
+      </ProfileRegion>
+      <ProfileImage id="footprint-image" theme={theme} x={486} y={196} width={434} height={234} label="Workplace / facility / local context" />
+      <ProfileRegion x={486} y={445} width={434} height={35}><ProfileText id="footprint-caption" theme={theme} size={13} muted>[Location and truthful caption; date if relevant]</ProfileText></ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-people" theme={theme} title="The people accountable for the work." eyebrow="08 / PEOPLE & EXPERTISE" folio="10">
+      <ProfileImage id="people-lead-image" theme={theme} x={40} y={196} width={266} height={164} label="Portrait / team at work" />
+      <ProfileImage id="people-delivery-image" theme={theme} x={346} y={196} width={266} height={164} label="Portrait / team at work" />
+      <ProfileImage id="people-specialist-image" theme={theme} x={652} y={196} width={268} height={164} label="Portrait / team at work" />
+      <ProfileRegion x={40} y={376} width={266} height={104}>
+        <ProfileText id="people-lead-name" theme={theme} size={22}>[Name / role]</ProfileText>
+        <ProfileText id="people-lead-expertise" theme={theme} size={16} muted>[Relevant expertise and what this person is accountable for.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={346} y={376} width={266} height={104}>
+        <ProfileText id="people-delivery-name" theme={theme} size={22}>[Name / role]</ProfileText>
+        <ProfileText id="people-delivery-expertise" theme={theme} size={16} muted>[Relevant expertise and what this person is accountable for.]</ProfileText>
+      </ProfileRegion>
+      <ProfileRegion x={652} y={376} width={268} height={104}>
+        <ProfileText id="people-specialist-name" theme={theme} size={22}>[Name / role]</ProfileText>
+        <ProfileText id="people-specialist-expertise" theme={theme} size={16} muted>[Relevant expertise and what this person is accountable for.]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-assurance" theme={theme} title="The standards we can stand behind." eyebrow="09 / CREDENTIALS & RESPONSIBILITY — OPTIONAL" folio="11">
+      <ProfileRegion x={40} y={196} width={880} height={282}>
+        <ProfileRow id="assurance-credential" theme={theme} number="01" title="[Credential / license]" detail="[Issuer, exact scope, current status, expiry, and verification source. Omit if not applicable.]" />
+        <ProfileRow id="assurance-quality" theme={theme} number="02" title="[Quality / governance]" detail="[A real process or policy, its owner, and evidence of how it is applied.]" />
+        <ProfileRow id="assurance-responsibility" theme={theme} number="03" title="[Responsibility]" detail="[A documented commitment or measured result. Distinguish future goals from achieved outcomes.]" />
+      </ProfileRegion>
+    </ProfileSlide>
+
+    <ProfileSlide id="profile-contact" theme={theme} cover title="Start a useful conversation." titleSize={48} eyebrow="10 / CONTACT" folio="12">
+      <ProfileImage id="contact-image" theme={theme} x={560} y={0} width={400} height={540} label="People / product / place" />
+      <ProfileRegion x={40} y={354} width={464} height={124}>
+        <ProfileText id="contact-name" theme={theme} size={21}>[Contact name / role]</ProfileText>
+        <ProfileText id="contact-email" theme={theme} size={18}>[Email] / [Phone]</ProfileText>
+        <ProfileText id="contact-website" theme={theme} size={18}>[Website] / [Office or time zone]</ProfileText>
+        <ProfileText id="contact-invitation" theme={theme} size={13} muted>[A clear reason to connect and the next conversation to have.]</ProfileText>
+      </ProfileRegion>
+    </ProfileSlide>
+  </CompanyProfile>;
+}

package/starter/templates/company-profile/template.json

@@ -0,0 +1,15 @@
+{
+  "name": "Company profile",
+  "description": "An architectural introduction to an organization: capabilities, sectors, people, and documented proof, with generous photography and a clear route to contact.",
+  "format": "16:9 · Company profile",
+  "documentFormat": "presentation",
+  "structure": [
+    "Twelve adaptable slides: introduce, explain, demonstrate, and connect.",
+    "A tall-image cover, numbered capability ledger, unequal image spread, and four-stage operating rail.",
+    "A two-slide case study separates project context from verifiable outcomes and attribution.",
+    "Location ledger and people portraits communicate presence without invented maps or scale.",
+    "Optional credential register states issuer, scope, status, and evidence.",
+    "Every image, metric, name, claim, and contact field begins as an explicit placeholder.",
+    "Native text and stable slide identities support corrections, comments, and reordering."
+  ]
+}

package/starter/templates/consulting-report/AGENTS.md

@@ -0,0 +1,11 @@
+# Consulting report
+
+Use this template as a soft foundation for a consulting document. Its character is clear hierarchy, consistent alignment, readable evidence, and useful navigation. The cover groups its content toward the bottom using native page alignment. The cover, type sizes, margins, and spacing are defaults, not a fixed rule system. A long title may need smaller type through `titleStyle`; a short report may work better with `cover={false}`. Rebalance the composition, adjust exhibit proportions, and adapt the rhythm to the actual reader and material. There is room for variation and creativity.
+
+The design research favored distinct title/body/note levels, clear section openings, exhibits with informative headlines, and sources close to the evidence. These are useful directions, not a mandatory writing method. Let the writer choose the content and its order. Add a summary or contents page only when it helps the document; do not force every report into the same outline. Use emphasis selectively so a reader can scan without every sentence competing for attention.
+
+Tables and charts need legible labels, units, and enough width. Prefer simplifying or reorienting a dense exhibit over shrinking its text beyond comfortable reading. Keep captions with figures and use existing native table header repetition. Choose a short `runningTitle` if the full title crowds the header. The cover is optional; page numbers follow the PDF's physical page order, including the cover.
+
+Use existing OpenDoc blocks and Forme's native Page, Fixed, View, Text, and Table flow. Keep variable prose breakable, and use Section for a heading with a short lead. Avoid custom text fitting, page splitting, simulated newspaper columns, or renderer patches. The theme supplies visual hierarchy, rhythm, and component treatments; document-specific design changes should stay local or use options that preserve shared defaults. Preserve stable IDs and accurate evidence.
+
+Review the actual PDF after adapting it. Shared changes need short and long specimens, table continuations, a second theme, and a working starter. Use Neutral for the catalog preview. Read `RESEARCH.md` for the formatting references and `README.md` for the component's options. Preserve unrelated documents and templates.

package/starter/templates/consulting-report/README.md

@@ -0,0 +1,13 @@
+# Consulting report
+
+A reusable starting layout for advisory reports, assessments, and recommendations. It combines an optional, bottom-aligned typographic cover with flowing A4 report pages. The cover uses native page `justifyContent: 'flex-end'`; content retains its normal spacing and remains breakable. Defaults are 54-point side margins (approximately 487 points of content width), 62-point body top and 58-point bottom margins, 11.5/16.675-point body type, and 10-point paragraph gaps. The running title and page numbers orient the reader. Fonts and colors come from the caller's theme.
+
+Pass `title`, `theme`, and ordinary OpenDoc blocks as `children`. Optional `subtitle`, `author`, `date`, `label`, and `coverNote` form the opening. `cover` defaults to true; set it to false for a short report whose title and body should share a page. No summary, contents page, argument, or section order is required.
+
+Use `titleStyle={{ fontSize: 32 }}` when a long title needs smaller type, or another native Forme text style for a purposeful variation. `runningTitle="A short report title"` provides a compact header; `false` omits it. Body page numbers reflect physical PDF page order, including an unnumbered cover. Opening text remains breakable; if an unusually long opening spans pages, shorten or restyle it after reviewing rather than relying on automatic fitting.
+
+Use ordinary `Section`, `Paragraph`, `Figure`, and `DataTable` blocks. A Section keeps only its heading and short lead together; the rest flows. The specimen uses native `style={{ breakBefore: true }}` on its comparison section to start a substantial table with its introduction on a fresh page; this is an authoring choice, not a layout requirement. A Figure keeps its image and caption together, so the complete group must fit on a page. DataTable uses Forme's native table continuation and repeated header rows. Place a descriptive heading above an exhibit when helpful, and keep source notes with it. Native charts currently have the workspace's known font-encoding limitation; use the established local `Media` workflow for charts and native `Image` rendering, as described in [the media guidance](../../docs/MEDIA.md).
+
+Supply verified `references` and use `Cite` within prose for the normal reference list. The layout specimens use explicit placeholder captions and synthetic table rows, with no invented business findings. `Specimen` in `preview.tsx` accepts sparse, typical, and long lengths plus an optional theme for review. The catalog always uses Neutral; `starter.tsx` creates an ordinary linked document.
+
+The template is an adaptable foundation. See [AGENTS.md](AGENTS.md) for design judgment and [RESEARCH.md](RESEARCH.md) for the formatting references. There is no custom typesetting, pagination, or fitting engine.

package/starter/templates/consulting-report/RESEARCH.md

@@ -0,0 +1,10 @@
+# Formatting references
+
+Reviewed on 8 September 2026 to inform this layout. These are examples of published consulting reports, not a universal consulting formatting standard. The choices below are design judgments; their measurements and branding are not copied into this template.
+
+- [BCG, Global Payments Report 2025](https://web-assets.bcg.com/25/91/2269153c468ca43684442f055cb0/2025-global-payments-report-sep-2025.pdf): visually inspected PDF pages 1, 4, and 7. The cover separates publication identity, headline, and date. The highlights page uses distinct levels for figures and explanation. The narrative/exhibit page aligns content consistently and gives the exhibit its own headline, units, source notes, and page furniture. Its two-column narrative is not reproduced here; this template uses a single native flowing column.
+- [McKinsey, Superagency in the workplace, January 2025](https://www.mckinsey.com/~/media/mckinsey/business%20functions/quantumblack/our%20insights/superagency%20in%20the%20workplace%20empowering%20people%20to%20unlock%20ais%20full%20potential%20at%20work/superagency-in-the-workplace-empowering-people-to-unlock-ais-full-potential-v3.pdf): reviewed the PDF's extracted structure and exhibit text, particularly PDF pages 8 and 13–15. Numbered exhibits use informative headlines and specify units, sample sizes, sources, and qualifications. This was a structural/text review, not a visual typography assessment.
+
+Applied here: a clear title/body/note hierarchy; optional cover; consistent alignment and navigation; ample exhibit width; nearby captions and source notes; and native table header repetition. Authors should keep evidence labels readable and use emphasis selectively. A summary or contents page may help a long report, but neither is required by the layout.
+
+The catalog specimen contains none of these reports' prose, data, charts, logos, or photography. Its content is expressly illustrative. Typography, color, and exact spacing remain adaptable to the document and its theme.

package/starter/templates/consulting-report/index.tsx

@@ -0,0 +1,44 @@
+import type { ReactNode } from 'react';
+import * as F from '@formepdf/react';
+import { TextSlot, Document, Heading, Paragraph, References, Page } from 'opendoc';
+import { themePage, type DocTheme } from 'opendoc/themes';
+
+export interface ConsultingReportProps {
+  title: string;
+  theme: DocTheme;
+  subtitle?: ReactNode;
+  author?: string;
+  date?: string;
+  label?: string;
+  cover?: boolean;
+  coverNote?: ReactNode;
+  runningTitle?: string | false;
+  titleStyle?: F.Style;
+  children: ReactNode;
+  references?: Parameters<typeof Document>[0]['references'];
+}
+
+/** An optional cover and ordinary flowing report pages, using native Forme layout. */
+export function ConsultingReport({ title, theme, subtitle, author, date, label, cover = true, coverNote, runningTitle = title, titleStyle, children, references }: ConsultingReportProps) {
+  const layoutTheme: DocTheme = theme.design ? theme : { ...theme, fontSize: 11.5, lineHeight: 1.45, paragraphGap: 10 };
+  const opening = <F.View style={{ ...theme.design?.title?.block, ...(cover ? theme.design?.cover?.block : undefined) }}>
+    {label && <Paragraph id="report-label" role="label" baseStyle={{ fontSize: 9, letterSpacing: 0.8, color: theme.accent, marginBottom: cover ? 56 : 16 }} style={{ ...theme.design?.title?.eyebrow, ...(cover ? theme.design?.cover?.eyebrow : undefined) }}>{theme.design?.title?.uppercaseEyebrow ? label.toUpperCase() : <TextSlot slot="label" from="label">{label}</TextSlot>}</Paragraph>}
+    <Heading id="report-title" level={1} baseStyle={{ fontSize: cover ? 38 : 30, lineHeight: 1.12, marginBottom: 20 }} style={{ ...theme.design?.title?.heading, ...(cover ? theme.design?.cover?.title : undefined), ...titleStyle }}><TextSlot slot="title" from="title">{title}</TextSlot></Heading>
+    {subtitle && <Paragraph id="report-subtitle" role="lead" baseStyle={{ fontSize: 17, lineHeight: 1.4, color: theme.muted, marginBottom: 24 }} style={{ ...theme.design?.title?.subtitle, ...(cover ? theme.design?.cover?.subtitle : undefined) }}><TextSlot slot="subtitle" from="subtitle">{subtitle}</TextSlot></Paragraph>}
+    {(author || date) && <F.View style={{ marginTop: cover ? 38 : 0, marginBottom: cover ? 32 : 22, borderTopWidth: 0.6, borderColor: theme.line, paddingTop: 14 }}>
+      {author && <Paragraph id="report-author" role="small" baseStyle={{ fontSize: 10, marginBottom: 6 }} style={{ ...theme.design?.title?.byline, ...(cover ? theme.design?.cover?.byline : undefined) }}><TextSlot slot="author" from="author">{author}</TextSlot></Paragraph>}
+      {date && <Paragraph id="report-date" role="small" baseStyle={{ fontSize: 10, color: theme.muted, marginBottom: 0 }} style={{ ...theme.design?.title?.byline, ...(cover ? theme.design?.cover?.byline : undefined) }}><TextSlot slot="date" from="date">{date}</TextSlot></Paragraph>}
+    </F.View>}
+    {coverNote && <Paragraph id="report-context" role="small" baseStyle={{ fontSize: 10, color: theme.muted, marginBottom: 24 }} style={cover ? theme.design?.cover?.byline : undefined}><TextSlot slot="coverNote" from="coverNote">{coverNote}</TextSlot></Paragraph>}
+  </F.View>;
+  return <Document title={title} author={author} theme={layoutTheme} references={references}>
+    {cover && <Page {...themePage(theme, { top: 72, bottom: 58, left: 54, right: 54 })} style={{ lineBreaking: 'greedy', justifyContent: 'flex-end', ...theme.design?.page?.style, ...theme.design?.cover?.page }}>{opening}</Page>}
+    <Page {...themePage(theme, { top: 62, bottom: 58, left: 54, right: 54 })} style={{ lineBreaking: 'greedy', ...theme.design?.page?.style }}>
+      {runningTitle !== false && (!theme.design || theme.runningHeader) && <F.Fixed position="header"><F.Text style={{ fontFamily: theme.body, fontSize: 8, color: theme.muted, borderBottomWidth: 0.5, borderColor: theme.line, paddingBottom: 8, ...theme.design?.furniture?.text, ...theme.design?.furniture?.header }}>{theme.design?.furniture?.uppercaseHeader ? runningTitle.toUpperCase() : runningTitle}</F.Text></F.Fixed>}
+      {(!theme.design || theme.runningFooter) && <F.Fixed position="footer"><F.Text style={{ fontFamily: theme.body, fontSize: 8, color: theme.muted, textAlign: 'right', ...theme.design?.furniture?.text, ...theme.design?.furniture?.footer }}>{theme.design?.furniture?.pageNumber === 'total' ? '{{pageNumber}} / {{totalPages}}' : '{{pageNumber}}'}</F.Text></F.Fixed>}
+      {!cover && opening}
+      {children}
+      <References headingBaseStyle={{ fontSize: 14, marginTop: 26, marginBottom: 10 }} />
+    </Page>
+  </Document>;
+}

package/starter/templates/consulting-report/preview.tsx

@@ -0,0 +1,39 @@
+import * as F from '@formepdf/react';
+import { DataTable, Figure, Heading, Paragraph, Section } from 'opendoc';
+import { neutral } from '../../themes';
+import { type DocTheme } from 'opendoc/themes';
+import { ConsultingReport } from './index';
+
+export const meta = { title: 'Consulting report', description: 'A Neutral formatting specimen with illustrative placeholders only.', kind: 'report' as const, theme: 'neutral' };
+const paragraph = 'This paragraph demonstrates the reading measure and spacing of the report. Its content is illustrative: it describes no client, market, or finding. In an authored document, the material would determine the section order and the evidence needed. The layout gives prose, headings, and exhibits a shared alignment while leaving room to adapt their size and emphasis.';
+
+export function Specimen({ length = 'typical', theme = neutral }: { length?: 'sparse' | 'typical' | 'long'; theme?: DocTheme } = {}) {
+  const sparse = length === 'sparse';
+  return <ConsultingReport title={meta.title} theme={theme} cover={!sparse}
+    subtitle={sparse ? undefined : 'A clear structure for reading, comparing evidence, and finding the next passage.'}
+    author={sparse ? undefined : 'Author or team name'} date={sparse ? undefined : 'Month / Year'}
+    coverNote={sparse ? undefined : 'Illustrative formatting specimen. All prose, exhibit areas, and table entries are placeholders; no business findings are claimed.'}>
+    <Section id="specimen-opening" title="A clear section opening" lead="A short opening sits with the heading. This is a placement example, not a prescribed report section.">
+      <Paragraph id="specimen-first-paragraph">{paragraph}</Paragraph>
+    </Section>
+    {!sparse && <>
+      {Array.from({ length: length === 'long' ? 9 : 1 }, (_, index) => <Paragraph key={index} id={`specimen-body-${index + 1}`}>{paragraph}</Paragraph>)}
+      <Section id="specimen-exhibit" title="Give the exhibit a useful headline" lead="This heading introduces an illustrative visual area. In a real report, its wording should reflect the evidence presented.">
+        <Figure id="specimen-figure" caption="Exhibit position. Labels, units, and legends belong inside the visual where they can be read." sourceNote="Source note position. Placeholder only; no source is claimed.">
+          <F.View style={{ height: 155, backgroundColor: theme.paper, borderWidth: 0.6, borderColor: theme.line, justifyContent: 'center', alignItems: 'center' }}>
+            <F.Text style={{ fontSize: 10, color: theme.muted }}>Full-width exhibit · Illustrative placeholder</F.Text>
+          </F.View>
+        </Figure>
+      </Section>
+      <Section id="specimen-comparison" style={{ breakBefore: true }} title="Make comparisons easy to follow" lead="Tables share the reading width. The example below uses synthetic labels and repeats its header if it continues.">
+        <DataTable id="specimen-table" caption="Illustrative comparison rows" columns={[{ label: 'Item', width: 1 }, { label: 'Description', width: 2 }, { label: 'Note', width: 1.4 }]}
+          rows={Array.from({ length: length === 'long' ? 30 : 5 }, (_, index) => [`Example ${index + 1}`, 'Placeholder entry for layout review', 'Illustrative only'])}
+          sourceNote="Synthetic table for formatting review. No measured or client data." />
+      </Section>
+      <Paragraph id="specimen-closing">The report continues in the author's chosen order. This closing placeholder checks that text after a table remains available and readable.</Paragraph>
+      <Heading id="specimen-reference-heading" style={{ fontSize: 14, marginTop: 26 }}>References</Heading>
+      <Paragraph id="specimen-reference" style={{ fontSize: 9, color: theme.muted }}>Reference placement specimen. Real references appear here only when cited; no source is being claimed.</Paragraph>
+    </>}
+  </ConsultingReport>;
+}
+export default Specimen;

package/starter/templates/consulting-report/starter.tsx

@@ -0,0 +1,15 @@
+import { ConsultingReport } from '../../templates/consulting-report';
+import { Paragraph } from 'opendoc';
+// @ts-ignore The selected local theme module is inserted when this starter becomes a document.
+import { theme } from "__OPENDOC_THEME_MODULE__";
+
+const title = "__OPENDOC_TITLE__";
+const themeId = "__OPENDOC_THEME__";
+export const meta = { title, description: 'A consulting report, ready for your material.', kind: 'report' as const, theme: themeId };
+export const provenance = { template: 'templates/consulting-report/index.tsx' };
+
+export default function Report() {
+  return <ConsultingReport title={title} theme={theme} label="REPORT" subtitle="Replace this placeholder with your report's purpose." author="Author or team name">
+    <Paragraph id="report-opening">Your report begins here. Replace this placeholder with your own material, and choose the sections and exhibits that serve the reader.</Paragraph>
+  </ConsultingReport>;
+}

package/starter/templates/consulting-report/template.json

@@ -0,0 +1,11 @@
+{
+  "name": "Consulting report",
+  "description": "An optional cover and structured report pages, with clear section openings, generous exhibit width, and consistent navigation. For advisory reports, assessments, and recommendations.",
+  "format": "A4 · Cover and report",
+  "structure": [
+    "An optional bottom-aligned cover gives the title, subtitle, author, and date a clear hierarchy. Short documents can begin directly with the body.",
+    "Consistent margins align section headings, prose, tables, and exhibits on a shared reading width.",
+    "Exhibits can pair a descriptive headline with a caption and source note. Native tables repeat their headers when they continue.",
+    "A running title and page numbers support navigation. References follow the authored content; no section order is prescribed."
+  ]
+}

package/starter/templates/editorial-essay/AGENTS.md

@@ -0,0 +1,11 @@
+# Editorial essay
+
+Use this template as a soft foundation for the essay, with room for variation and creativity. It suggests a narrow, continuous literary reading column, never an argument or writing method. Its measurements are starting values: reduce the title size for a long title, rebalance the opening space, or adjust the measure and paragraph rhythm to suit the text. Preserve a readable hierarchy and sustained flow rather than every specimen detail.
+
+Close leading, first-line indents, and modest 6-point paragraph gaps are the current baseline. Flush openings after headings or visual breaks, a quiet byline, and a distinct standfirst support that character. Adapt or omit these treatments when another choice better serves the document; long prose must still flow naturally.
+
+Headings can be sparse or more frequent according to the material. Occasional visuals may span the text width, with a caption beneath. References normally sit quietly at the end. The starting design is restrained, but it does not prohibit a purposeful departure or impose a mandatory outline.
+
+The layout wraps body blocks in `Prose`, which expands author components before applying paragraph flow. Keep ordinary `Paragraph` blocks and their IDs; don't add leading spaces to content or manually split lines. `Prose` inserts a measured em-space run for the first line and leaves continuation lines flush across page breaks. Keep it scoped to body prose, never captions or references. Do not nest `Prose` regions. Read `docs/PROSE.md` before changing this compatibility helper.
+
+The caller supplies the theme; the template's type sizes and spacing remain adaptable. Preview the catalog specimen with the shared Neutral theme. Keep document-specific variations local so other documents retain their existing layout. Preserve stable content IDs and review all pages after a layout change; shared changes need sparse and long specimens as well. Do not change unrelated templates or documents.

package/starter/templates/editorial-essay/README.md

@@ -0,0 +1,11 @@
+# Editorial essay
+
+A layout component for continuous, single-column essays. It sets A4 geometry, 105-point side margins, an open title/byline/standfirst arrangement, close 11/15.62-point body typography, and discreet page numbers. Openings are flush left; later paragraphs have a 1½-em first-line indent, with 6-point gaps between body paragraphs. Prose flows through as many pages as it needs. Fonts and colors come from the caller's theme.
+
+Use `EditorialEssay` with `title`, `theme`, optional `author` and `standfirst`, and ordinary OpenDoc blocks as `children`. Supply verified `references` to the component and use `Cite` within the text; cited references appear at the end. There is no mandatory content outline or JSON schema. Content may use the document's own data contract when useful.
+
+The template uses the [Prose compatibility helper](../../docs/PROSE.md) to indent body paragraphs after author components have expanded. It resets at headings and figures, leaves captions and reference entries alone, and preserves comment targets. Forme still handles line wrapping and pagination; source text contains no manually inserted whitespace or line breaks.
+
+`preview.tsx` supplies a Neutral layout specimen with clearly identified placeholders, including visual and reference positions. Its `Specimen` export also accepts `length="sparse"` or `length="long"` for flow checks. Specimen-generated IDs belong only to the fixed proof; authored content must keep stable semantic IDs.
+
+`starter.tsx` becomes a new ordinary document when the user chooses this template. Creation replaces the title/theme sentinels safely and imports the generated `./theme` adapter; layout imports remain linked to this folder. Preserve the adapter and `assets.json` in each instance. Changing an existing essay's theme must not change this template's geometry. Read `AGENTS.md` before altering its layout.