METHOD / PROPOSED ENGAGEMENT FRAMEWORK

A controlled transition from unformed idea to working system.

The PHASE method structures strategic decisions, identity formation, digital experience, and production as one controlled sequence.

  1. 01Input
  2. 02Interpretation
  3. 03Decision
  4. 04Production
  5. 05Verification
  6. 06Output

This operating lens clarifies the work inside the four frozen Method stages; it does not replace or extend them.

It is a proposed engagement model for this self-initiated fictional practice, not evidence of completed client engagements, validated delivery performance, or production deployment.

METHOD STATUS / TRUTH BOUNDARY

A framework to review, not a proven-process claim.

FOUR-STAGE SEQUENCE / HOW IT IS FORMED

One sequence, four controlled transitions.

The existing Homepage stage names and order remain authoritative. This route defines the inputs, decisions, evidence, and exit condition behind each stage.

  1. 01 / Unformed Input

    Threshold

    WORK IN THIS STAGE

    Define the context, constraints, readiness, scope, and decision boundary before a direction is formed.

    REQUIRED INPUTS

    • Project-owner brief
    • Known business facts and hypotheses
    • Available evidence, assets, constraints, and decision roles

    KEY DECISIONS

    • Problem boundary
    • Audience and outcome hypotheses
    • Evidence gaps
    • Authorized scope and exclusions

    WORKING OUTPUTS

    • Working brief
    • Scope and assumption register
    • Evidence request
    • Decision map

    APPROVAL GATE

    Scope Gate

    EVIDENCE STATUS

    Supplied facts are separated from hypotheses; missing evidence remains visibly unresolved.

    EXIT CONDITION

    A documented scope, truth boundary, owner map, and approved next decision.

    PASS / PROCEED

    Scope Gate approval permits progression to Synthesis.

    HOLD / ITERATE

    Missing evidence, unresolved decisions, or absent approval return the stage to review; the sequence does not silently advance.

  2. 02 / Strategic Structure

    Synthesis

    WORK IN THIS STAGE

    Organize approved facts, positioning hypotheses, evidence, and system requirements into one strategic structure.

    REQUIRED INPUTS

    • Approved Threshold record
    • Client-supplied or independently verifiable evidence
    • Content and technical requirements

    KEY DECISIONS

    • Positioning direction
    • Messaging hierarchy
    • Information architecture
    • Claim boundaries

    WORKING OUTPUTS

    • Strategic synthesis
    • Proposed narrative architecture
    • Content model
    • Direction options

    APPROVAL GATE

    Direction Gate

    EVIDENCE STATUS

    Every material claim is evidenced, explicitly hypothetical, or held from progression.

    EXIT CONDITION

    One approved strategic structure with content and truth conditions recorded.

    PASS / PROCEED

    Direction Gate approval permits progression to Formation.

    HOLD / ITERATE

    Missing evidence, unresolved decisions, or absent approval return the stage to review; the sequence does not silently advance.

  3. 03 / Visible System

    Formation

    WORK IN THIS STAGE

    Translate the approved synthesis into a visible identity, interface, and communication system.

    REQUIRED INPUTS

    • Approved strategic structure
    • Rights-cleared content and assets
    • Accessibility and technical constraints

    KEY DECISIONS

    • Identity direction
    • Page and component systems
    • Responsive behaviour
    • Content and interaction states

    WORKING OUTPUTS

    • Visible system source
    • Page and component specifications
    • Responsive states
    • Content and asset register

    APPROVAL GATE

    Content and Truth Gate

    EVIDENCE STATUS

    Content accuracy, asset rights, and presentation claims require documented owner review.

    EXIT CONDITION

    An approved visible system with production scope and known limitations defined.

    PASS / PROCEED

    Content and Truth Gate approval permits progression to Current Form.

    HOLD / ITERATE

    Missing evidence, unresolved decisions, or absent approval return the stage to review; the sequence does not silently advance.

  4. 04 / Production-ready Source

    Current Form

    WORK IN THIS STAGE

    Consolidate approved structure into production-ready source, QA evidence, and a bounded handoff state.

    REQUIRED INPUTS

    • Approved visible system
    • Final content and local assets
    • Authorized technical access and release criteria

    KEY DECISIONS

    • Implementation boundary
    • Accessibility and performance acceptance
    • Known limitations
    • Deployment ownership

    WORKING OUTPUTS

    • Approved production source
    • QA evidence
    • Known-limitations register
    • Deployment instructions

    APPROVAL GATE

    Production Gate

    EVIDENCE STATUS

    Source readiness is evidenced locally; deployment, launch, and commercial results are not inferred.

    EXIT CONDITION

    Documented handoff, explicit deployment boundary, and a separately owned Release Gate.

    PASS / PROCEED

    Production Gate approval permits bounded handoff; deployment still requires a separate Release Gate.

    HOLD / ITERATE

    Missing evidence, unresolved decisions, or absent approval return the stage to review; the sequence does not silently advance.

APPROVAL AND EVIDENCE GATES

Progression depends on visible decisions.

These are proposed governance gates. They do not represent real client signatures, approval timing, legal review, or launch authorization.

  1. 01 / 05

    Documented approval required.

    Scope Gate

    Required Evidence
    Brief, constraints, assumptions, exclusions, and identified decision owners.
    Decision Owner
    Shared decision led by the project owner.
    Approval State
    Documented approval required.
    Cannot Proceed
    Strategic direction cannot proceed.

    IF SATISFIED Direction work

  2. 02 / 05

    Documented direction approval required.

    Direction Gate

    Required Evidence
    Strategic synthesis, alternatives considered, evidence register, and claim boundaries.
    Decision Owner
    Shared decision; business facts remain project-owner owned.
    Approval State
    Documented direction approval required.
    Cannot Proceed
    Identity and experience formation cannot proceed.

    IF SATISFIED Formation work

  3. 03 / 05

    Documented content and truth approval required.

    Content and Truth Gate

    Required Evidence
    Final copy, factual sources, asset rights, regulated-claim review, and known gaps.
    Decision Owner
    Project owner, with external specialist review where required.
    Approval State
    Documented content and truth approval required.
    Cannot Proceed
    Production source cannot be treated as approved.

    IF SATISFIED Production-source work

  4. 04 / 05

    Documented production-source acceptance required.

    Production Gate

    Required Evidence
    Approved design source, implementation inventory, responsive and accessibility QA, performance baseline, and limitations.
    Decision Owner
    Shared decision with the authorized technical owner.
    Approval State
    Documented production-source acceptance required.
    Cannot Proceed
    Handoff cannot be marked production-ready.

    IF SATISFIED Bounded handoff

  5. 05 / 05

    Separate release authorization required.

    Release Gate

    Required Evidence
    Environment ownership, deployment plan, security and privacy review, operational responsibilities, and rollback decision.
    Decision Owner
    Project owner and authorized deployment specialists.
    Approval State
    Separate release authorization required.
    Cannot Proceed
    Deployment and public launch cannot proceed.

    IF SATISFIED Separately authorized deployment

ENGAGEMENT ROLES

Responsibility follows evidence and authority.

Business facts

Client / Project-owner Responsibility

Supply and approve current, accurate business facts.

Legal claims

External Specialist Responsibility

Qualified legal review is required; PHASE does not provide legal confirmation.

Regulatory claims

External Specialist Responsibility

Qualified domain review is required; PHASE does not provide medical, financial, security, or compliance certification.

Content accuracy

Client / Project-owner Responsibility

Approve factual accuracy and release-ready copy.

Asset rights

Client / Project-owner Responsibility

Confirm ownership, licensing, consent, and permitted use.

Strategic and design formation

Practice Responsibility

Prepare proposed structures and source within the approved evidence and scope boundary.

Direction and acceptance

Shared Decision

Record options, trade-offs, approvals, exceptions, and known limitations.

Technical access

Client / Project-owner Responsibility

Authorize credentials, environments, systems, and access duration.

Hosting

External Specialist Responsibility

Hosting contracts, configuration, security, monitoring, and continuity require an identified operator.

Deployment authorization

Shared Decision

Release requires project-owner authorization and an accountable technical operator.

Post-launch operation

Client / Project-owner Responsibility

Ongoing content, security, maintenance, analytics, transactions, and incident response remain separately owned.

PRODUCTION HANDOFF

Source readiness ends before release authority begins.

  1. 01 / DEMONSTRATIONProposed presentation and system states may be reviewed.
  2. 02 / IMPLEMENTATIONApproved source and local QA may support handoff.
  3. 03 / DEPLOYMENTRequires a separate Release Gate and environment owner.
  4. 04 / VERIFICATIONIndependent or production validation is not inferred.
  5. 05 / OUTCOMECommercial and operational results are not inferred.

RETURN ROUTE / CAPABILITIES

Review what this sequence can form.

Capabilities defines the proposed offer, deliverable families, engagement boundaries, evidence requirements, and production limits governed by this Method.

THIS ROUTE
HOW approved work moves through decisions and gates
RETURN ROUTE
WHAT problems, artifacts, and boundaries the offer contains