Proposal Workflow

Purpose

The proposal workflow connects commercial context, templates, sections, AI-assisted drafting, review, approval, export, and outcome tracking. The public doc should describe the lifecycle rather than list internal routes.

Operating Context

This documentation belongs to the Operations layer of ENGiOS. It should help readers understand the product capability, its governance model, and its relationship to the wider operating system.

Public Detail Boundary

Public documentation should explain intent, lifecycle, roles, and decision points. It must avoid secrets, hosts, full endpoint inventories, private paths, operational commands, and raw internal audit detail.

Writing Guidance

Use concise product language, name the related ENGiOS modules, and state what remains future scope. When an internal source contains implementation detail, translate it into capability-level language.

Acceptance Criteria

A reader should understand what the workflow governs, what signal it creates, which modules it connects, and why the capability matters for engineering operations.