Agent factory

Deeper page · Manufacturing loop

One useful outcome first.The factory comes after.

QuoteForge is the opening specialist — controlled quote and scope preparation. This page is the manufacturing loop around that specialist: boundary, sources, evaluation, controlled work and evidence. It is not a product catalogue and not a claim of production readiness.

Illustrative map · intended operating boundary · not a live connection diagram

Evidence classIllustrative map

System map

What sits around the model

The model helps interpret and draft. The surrounding control plane keeps business truth, deterministic checks, human authority and evidence in the same loop.

Owner supplies

Business truth

The material the specialist is allowed to use.
  • Approved documents and rules
  • Examples and edge cases
  • Named owner and source dates
Business truth enters the control plane

LYC control plane

Manufacture the specialist

  1. Structure

    Facts, fields, sources, conflicts and unknowns become visible.

  2. Bound

    Authority, permissions and safe-stop conditions are written down.

  3. Evaluate

    Normal, missing-information, adversarial and regression cases run first.

Model work

Interpret language, ask, classify and draft.

Deterministic work

Calculate, validate and enforce the written contract.

The control plane produces review-ready work

Before any commitment

Controlled work

Useful output with uncertainty and authority still visible.
  • Draft, handoff or next-action queue
  • Safe stop when information is missing
  • Receipt of what happened

Owner decides

Human decision gate

The business keeps the consequential choices.
  • Approve, correct, reject or stop
  • Own price, promise, send and commitment
  • Widen authority only after evidence

Evidence stays attached

Receipt and next gate

Each run leaves a compact record for review and repair.
  • Sources, versions and unknowns
  • Decision, actor and outcome
  • Continue, revise or stop

This is an explanatory map of the intended operating boundary, not a claim that every connection is live. The public witness uses fictional information, no provider calls and zero external effects.

Next useful step

If this names a bottleneck you own, show us one real workflow. We map boundaries before proposing a pilot.

The build loop

Every stage leaves something reviewable behind.

A plausible answer is not business truth. Each hand-off makes the source, authority, uncertainty and next decision easier to inspect. This is the manufacturing sequence after the first useful outcome is understood.

  1. Bound one workflow

    Name one painful, repeatable outcome, one accountable owner and the decisions that must remain human. Capture a baseline before promising automation.

    Workflow boundary + baseline

  2. Preserve business truth

    Collect the minimum approved sources, rules, examples and exclusions. Conflicts and unknowns stay visible instead of being silently resolved.

    Source manifest + operating pack

  3. Draft the specialist

    Map the workflow to a specialist blueprint: model work, deterministic work, human authority, required fields, permissions and safe-stop conditions.

    Blueprint + owner field map

  4. Test synthetic work

    Run normal, missing-information, adversarial, safe-stop and regression cases against the fixed configuration before any real business record is admitted.

    Evaluation scorecard + corrections

  5. Pilot with control intact

    Use draft-first outputs with human review, receipts and a measured day-30 decision. Continue, expand or stop remains the owner’s choice.

    Pilot evidence + continuation decision

What the owner can inspect

Drafts and evidence before access.

The local setup flow is deliberately review-first. It can carry a business from discovery to a field-mapped configuration draft without uploading raw documents, calling a provider or activating an agent.

Discovery draft

Requires owner review

The workflow, owner, source manifest, storage boundary and controls are recorded without admitting raw file contents.

Specialist blueprint

Requires owner review

The authority split, source-alignment gaps, required fields and synthetic-evaluation gate are made explicit.

Configuration draft

Ready for synthetic evaluation

Every required field is mapped to a human label, description and admitted source reference. Activation is still disabled.

Permission by design

Useful work without quiet authority creep.

The specialist is allowed to be helpful inside a written boundary. It is not allowed to turn uncertainty into a commitment. This is the intended operating split, not a certification.

Inside the boundary

  • Retrieve approved knowledge inside the agreed workflow
  • Structure incoming information and identify what is missing
  • Apply deterministic calculations owned by code
  • Prepare drafts, handoffs and next-action suggestions
  • Show sources, uncertainty, permissions and receipts

A human still owns

  • Invent a price, rule or source when the business is silent
  • Approve a canonical rule or widen its own permissions
  • Send messages, book work, invoice, charge or publish
  • Make a binding customer commitment
  • Turn a synthetic witness into a production claim

Fictional factory witnesses

One manufacturing loop. Different business truth.

These sites are artificial businesses used to pressure-test the shared platform. They are not customers, case studies or proof of commercial results. QuoteForge is the opening wedge; the other lanes remain research witnesses.

Opening wedge · fictional

QuoteForge

Southern Trades Services

Enquiry intake, missing-detail triage and a deterministic quote draft from a fictional approved pricebook.

Human boundary: The owner keeps site judgement, final price, approval and sending.

Research witness · fictional

LeadForge

Harbourlight Motors

Vehicle-enquiry qualification and a structured salesperson handoff for a fictional dealership.

Human boundary: The agent does not make finance decisions, contact the buyer or commit the deal.

Research witness · fictional

OpsForge

Kōwhai Office Supply

Business-order intake and proposal preparation using a fictional office-supply catalogue.

Human boundary: The agent does not confirm stock, negotiate a price or promise delivery.

Deeper · decision layer

Name the bottleneck before buying the tool.

GrowthForge is one business-facing agent inside the wider LYC system. It takes an owner's stated goal, workload evidence, constraints and candidate interventions, then compares conservative, expected and optimistic ranges so the next move can be inspected against the owner's own limits.

Hard boundary

GrowthForge does not install the chosen tool, approve a budget, change a business rule or promise growth. The factory builds a separate customer specialist only after the owner approves the next boundary.

Bottleneck

Name the stage where time, capacity, cost or risk is constraining the work.

Viability range

Show returned capacity, net value, review load and payback against the owner's limits.

Decision gate

Return viable, more information, not viable, human review or safe stop—with evidence and unknowns visible.

The first real business

Replace synthetic truth only after permission is earned.

A first customer enters through a measured, draft-first pilot — not by being treated as another demo tenant. The same factory must survive the owner's real rules, sources and corrections.

Read the customer journey →
  1. Written permission for discovery
  2. One bounded workflow and one named owner
  3. A measured baseline: time, corrections, missing fields and escalations
  4. Minimum approved sources and an owner-signed operating pack
  5. Synthetic and, where permitted, owner-approved historical evaluation
  6. A draft-first 30-day pilot with a day-30 continuation decision

Honesty

The examples on this page are fictional and synthetic. They demonstrate the manufacturing loop, not customer results. QuoteForge is the first specialist under discussion; later lanes are research witnesses only. Production readiness remains a separate gate.

Have one workflow worth pressure-testing?

Tell us what keeps stealing time. We will map the smallest sensible boundary before proposing a larger system.