Skip to main content
AI
AIClouds.store

Documented operating-cycle design

One bounded cycle, sixteen visible stages.

The workflow below is the local CompanyOS operating-cycle index translated into plain English. It describes intended contracts, handoffs and recovery routes—not proof that every stage has executed or succeeded.

Inventory

16 versioned operating-cycle stages

How to read it

A defined stage is a design, not evidence of execution or success.

Authority

Protected outreach and production effects require the applicable human approval or review path.

Evidence boundary: CompanyOS source files and local simulations document architecture and invariants. They do not establish live customer operations, successful outreach, payment, or public production.

OC-01 through OC-16

The complete operating cycle

The stages are grouped by their documented role in the cycle. A lead may branch to recovery, review, archive or a prior stage; the numbered inventory remains the source map.

Stages 1–3

Discovery and qualification

Choose a bounded market, preserve provenance, then qualify evidence.

  1. OC-01

    Select market cell and inspect usable lead inventory

    Set one evidence-bounded market and check existing inventory before new discovery.

  2. OC-02

    Discover real businesses and preserve provenance

    Collect bounded public-source observations while retaining identity, timestamps and uncertainty.

  3. OC-03

    Audit digital condition score the lead and decide whether production is justified

    Separate evidence of website opportunity from assumptions about intent or ability to pay.

Stages 4–6

Planning, build and independent QA

Bind content to facts, assemble a candidate and test it independently.

  1. OC-04

    Build the verified fact pack and select the approved sector baseline

    Separate confirmed facts, uncertainty and prohibited claims before planning a site.

  2. OC-05

    Generate the nearly finished demo and validate its content

    Produce a versioned release candidate within the verified build contract.

  3. OC-06

    Independently test visual semantic logical and commercial quality

    Check the candidate, classify defects and return bounded remediation work when needed.

Stages 7–11

Preview, outreach and engagement

External contact and owner interaction stay inside explicit review boundaries.

  1. OC-07

    Publish the private preview and render the approved outreach packet

    Package a reviewable preview and bounded outreach materials; preparation is not dispatch.

  2. OC-08

    Run the bounded verified-business-email sequence

    Apply suppression, reply and idempotency checks before any permitted message.

  3. OC-09

    Decide whether to mail and submit the approved postcard

    Keep physical outreach inside a reviewed template, address, budget and suppression envelope.

  4. OC-10

    Monitor real engagement and determine lead temperature

    Distinguish meaningful signals from weak proxy traffic and preserve the evidence reason.

  5. OC-11

    Handle owner conversation questions and reasonable pre-sale changes

    Route authenticated owner requests through a bounded change and review loop.

Human review gate: Outreach is not implied by a workflow definition. Protected outreach effects such as a new channel, template, budget or exception follow the applicable human approval or review path; routine actions may proceed only inside the current approved envelope.

Stages 12–16

Sales, approval, handoff, archive and learning

Resolve the outcome safely, then return evidence to the next cycle.

  1. OC-12

    Present the approved offer and resolve the domain route

    Use the active price and domain context to present a bounded offer.

  2. OC-13

    Resolve exceptions create the payment route and confirm settlement

    Escalate protected exceptions and require reliable settlement evidence.

  3. OC-14

    Prepare production and activate the paid customer service

    Freeze the sold release, verify rollback readiness and respect the publication boundary.

  4. OC-15

    Close non-converting leads and apply dormant archive or removal policy

    Stop follow-up where required while keeping eligible evidence recoverable.

  5. OC-16

    Record outcomes learn within authority report and restart the loop

    Reconcile outcomes and propose bounded improvements only from declared evidence.

Production boundary: OC-14 describes a handoff contract. It does not mean a public customer site has been deployed. Public production, DNS, irreversible changes and customer commitments remain human-reviewed decisions.

Continue exploring the local candidate

Read the architecture and role directory, or return to the AI Clouds Company OS overview.

Architecture Digital team Back to AI Clouds Company OS