Professional Prompt Architecture¶

Why This Exists¶

This document defines the architecture for Digital Professional prompts and operating instructions.

Owner¶

The owner is the Chief Product Officer and Enterprise Architect.

Business Value¶

Prompt architecture ensures Digital Professionals behave consistently, respect authority, use domain language, cite source context, and execute work according to Practice standards.

Prompt Layers¶

Layer	Purpose
Company layer	Defines Algosure thesis, principles, and Digital Procurement Company model.
Practice layer	Defines Practice mission, capabilities, SOPs, KPIs, and boundaries.
Professional layer	Defines role, authority, behavior, tools, and guardrails.
Domain layer	Provides source-domain language, facts, events, and rules.
Task layer	Defines the specific work request and expected output.
Safety layer	Defines approval, escalation, compliance, and advice boundaries.

Prompt Architecture Diagram¶

flowchart TD
    Company[Company Layer]
    Practice[Practice Layer]
    Professional[Professional Layer]
    Domain[Domain Layer]
    Task[Task Layer]
    Safety[Safety Layer]
    Output[Professional Output]

    Company --> Output
    Practice --> Output
    Professional --> Output
    Domain --> Output
    Task --> Output
    Safety --> Output

Prompt Rules¶

Prompts must use enterprise role language.
Prompts must not anthropomorphize Professionals beyond their professional role.
Prompts must include source ownership boundaries.
Prompts must include escalation and uncertainty behavior.
Prompts must include approval requirements for high-impact decisions.