Enterprise Operations

The Enterprise Operations vertical scopes generation to internal business workflows: process documentation, incident management, onboarding, training, change management, partner enablement, knowledge management, and executive communications. Use it when content is written for internal audiences, requires operational precision, must define ownership and accountability, or needs to function as executable process guidance rather than general information.

What this vertical enforces

Each rule is read from the vertical’s configuration and checked against the finished draft at the Quality Gate, before publication. A draft that fails a blocking rule is sent back for revision or the run fails; it is not published with the defect.

Rule	Setting	Effect
Access	Starter	Requires Starter access or higher. Requests from accounts below it are refused (HTTP 403) before any credit is charged, from Studio or the API.
Source minimum	3 sources	Research must return at least 3 usable sources or no draft is written. Templates that declare citations optional or forbidden are exempt.
Mandatory disclaimers	1	Inserted by the formatter when absent, then confirmed present at the gate. A draft missing one is blocked.
Forbidden claims	4	Any occurrence blocks the draft, unless the sentence negates the claim (“we cannot guarantee…”).
Domain verification	Advisory, 2 verifiers	Findings are recorded in the document’s passport and shown to reviewers. They do not block publication.

Mandatory disclaimers

This content is operational guidance and should be reviewed against internal policies, legal obligations, security requirements, and stakeholder approvals before implementation.

Claim rules

Phrase	Rule	When unmet
guaranteed ROI	Never used	Blocks
zero risk	Never used	Blocks
no approval needed	Never used	Blocks
fully compliant by default	Never used	Blocks

Matching is by phrase, case-insensitive. A paraphrase of a forbidden claim is not caught by this rule; it is one reason human review remains required for regulated content.

Domain verification

Verifier	What it does not establish
`enterprise.availability`	Checks that a stated downtime budget is attainable under the availability target beside it, for any length the named period can have; it does not establish that the commitment was met, that measurement is sound, or that exclusions are reasonable.
`common.quantities`	Checks internal numeric consistency patterns; it does not establish that an external factual claim is true.

A verifier that cannot decide an object reports it as unverifiable, which is recorded separately from a pass. See Content Governance for how verdicts reach the passport.

Research policy

These settings shape which sources research gathers and how they rank. They influence evidence quality; they are not checks on the finished draft.

Setting	Value	Effect
Preferred domains	`bcg.com`, `forrester.com`, `gartner.com`, `hbr.org`, `iso.org`, `mckinsey.com`, `nist.gov`	Ranked as high-authority sources.
Excluded domains	`quora.com`, `reddit.com`	Scored at zero authority, so they are not relied on.
Recency	18-month half-life	A source’s recency weight halves every 18 months; older sources rank lower but are not excluded.

Catalog scope

This vertical permits 28 templates and 41 style profiles. A request for a template or style outside the allowlist is refused (HTTP 422); it is not silently substituted. Explicitly blocked: TV Pilot Script Generator, Feature Screenplay Generator, Series Bible.

Recommended combinations

Use case	Template	Style profile	Best for
Process documentation	Standard Operating Procedure	Developer Experience Writer	Repeatable, step-by-step operational procedures with ownership
Incident review	Incident Postmortem	Developer Experience Writer	Blameless reliability reviews with timeline and corrective actions
Customer onboarding	Customer Onboarding Guide	Knowledge Base Support Writer	Structured onboarding with milestones, steps, and success criteria
Internal training	Internal Training Manual	Learning Experience Architect	Modular training content with objectives, exercises, and competency checks
Org change rollout	Change Management Plan	Executive Summary	Stakeholder impact, communication cadence, and resistance mitigation
Partner activation	Partner Enablement Kit	Campaign Strategist	Co-sell playbooks, positioning, and channel partner activation
Self-serve support	Knowledge Base Article	Knowledge Base Support Writer	Searchable, self-serve support content structured for deflection
Leadership alignment	Executive Decision Brief	Executive Summary	Decision-ready briefs with options, recommendation, and decision criteria
Competitive intel	Competitive Battlecard	Campaign Strategist	Sales-ready objection handling, positioning, and competitive contrast
Product specs	Product Requirements Document	Developer Experience Writer	Feature scope, user stories, acceptance criteria, and technical constraints
Data governance	Data Quality Assessment	Investment Committee Analyst	Completeness, accuracy, consistency scoring, and remediation priorities
Quarterly review	Quarterly Business Review	Executive Summary	Performance against targets, key initiatives, and Q+1 priorities

Inputs that change the result

Supply these where they apply. Each one narrows the draft or gives research something specific to find:

Document type and intended use
Audience: team, role, or organizational level
Process scope and boundaries
Tool, system, or product context
Roles and ownership structure
Whether the output is for internal use, partner distribution, or leadership review
Existing process baseline or prior version if available
Compliance or audit requirements
Timeline or deadline context
Whether escalation paths and exception handling are required
Success criteria or completion definition

For operational content, specify the audience role, process scope, tool context, and whether ownership and escalation structure should be included. These details directly improve step precision and structural completeness.

When to use another vertical

Content need	Better vertical
Developer documentation for external audiences	SaaS and Tech
Customer-facing marketing and growth content	General or SaaS and Tech
Legal, compliance, or regulatory documentation	Legal and Compliance
Financial reporting or investment analysis	Fintech
Healthcare operations with clinical claims	Healthcare and Medical AI
Policy briefs or government communications	Political and Policy

Limits

The rules above check the draft against this vertical’s configuration. They do not establish that the content is accurate, current, or appropriate for a particular reader or jurisdiction.
Research policy ranks sources; it does not guarantee that any particular authority was consulted.
Required reviews and their qualifications are set by Policies and the template, not by the vertical alone.

Verticals

How verticals combine with templates and style profiles.

Content Governance

The Quality Gate, verification verdicts, and the passport.