← Architecture overview

ISH TEAM / WORKFLOW REVIEW

The thinking behind
Commercial OS.

A shared review for Ronald and the team. Follow the document, the assistance and the pricing decisions, then tell us what needs changing or explaining.

FOUR CONNECTED WORKFLOWS

Explore the system.

Open interactive diagram ↗

Follow the invoice from the workspace through checks, durable records and reviewed document output.

The diagram highlights the selected workflow. Open it separately for search, zoom and guided exploration. The explanations and source references below remain available without using the diagram.

Share architecture feedback

Describe a workflow question, missing connection or proposed correction. Feedback is saved for review when you select Send feedback.

Please leave out passwords, customer records and banking details. How feedback is handled

Review and send the email yourself. Unsent form text stays available while you switch workflows during this visit.

01 · THE DOCUMENT

A controlled path from draft to issue.

Your workspace checks the requested edit, your authority and the current invoice version. Approved actions are recorded with the business information so the team can follow what changed.

At issue, the renderer preserves the invoice content and checks the PDF before delivery. Existing issued documents stay protected from later price-book changes.

02 · AI ASSISTANCE

Helpful proposals. Explicit control.

Lerato uses the active document and your request to prepare a proposed action. The application checks the proposal, and you review and approve changes before they are applied.

An inspection can explain a problem without editing the invoice. A model suggestion is not verified supplier evidence. Server checks and a current document version remain necessary before applying a change.

03 · PRICING

Separate evidence from judgement.

The common resolver selects eligible price evidence and approved cost rates by region and scope. Source, supplier, date and unit travel with the result. A current project cost can take priority within that project.

An invoice selling-price adjustment remains a separate decision. Fresh local supplier evidence still needs to be maintained; the software does not certify an old observation as today’s delivered price.

04 · BRR AND REVIEWED QUOTES

Keep three commercial decisions separate.

The saved budget assessment preserves its package terms and evidence. An unconfirmed area or scope keeps the budget comparison provisional. A reviewed quotation needs the actual work, scope reference, checked price excluding VAT, price reference and exclusions.

The review is tied to the assessment digest so an older form cannot silently use changed terms. The assessment-service fee has its own invoice workflow. A reviewed estimate is not independent cost verification, and client BRR reports remain behind the wording-approval gate.

05 · REUSE

A foundation for future clients.

Shared AI, rendering and pricing capabilities are separated from the ISH commercial application. The course follows the same principle: reusable instruction with customer-specific branding and approved examples.

Future client onboarding and tenant isolation require their own verified rollout. This diagram does not claim that every future customer configuration has already been deployed.

YOUR CONNECTED WORKSPACE

Work, learn and review.

Commercial workspace

Prepare quotations and invoices, review proposed changes and keep approved documents protected.

Open Commercial OS →

Academy

Eleven available lessons explain civil quotations, invoicing, BRR and Settings. Begin with lesson 01, practise safely and return to your saved playback position. Express training remains hidden until the feature is live.

Open the Academy →

Retail plans

Compare the monthly service, onboarding and scoped assistance for your company.

Explore pricing →

BUSINESS RESPONSIBILITIES

Understand each part.

ISH user
  • An active ISH user is loaded from the commercial user record.

Web workspace
  • The whole invoice page supports section selection and movement.

  • The BRR review form collects scope, references, price and exclusions.

Commercial API
  • The API routes invoice changes through authenticated business handlers.

  • BRR assessment and reviewed quotation routes are implemented here.

Tool execution
  • Explicit form actions use the tool registry and approval/audit records.

  • Only registered handlers are selected for execution.

Business records
  • SQLAlchemy connects to the configured Business records database.

  • Transactional response receipts support recovery after a lost response.

Identity & access
  • The server verifies the JWT audience and signature.

  • Protected routes resolve the current authenticated user.

Assistance service
  • The source defaults to Assistance service and Lerato assistance; environment values can override defaults.

  • The provider adapter applies model, timeout and output controls.

Price intelligence
  • Eligible evidence is selected with region, freshness, validity and unit checks.

  • Approved project or company costs are a distinct controlled input.

Document renderer
  • PDF review uses the configured vision model and every page, independently of assistant drafting.

  • Method-statement drafts retain audited wording per quote revision and restore damaged caches from Business records.

  • The delivered PDF is checked against its file hash and gate receipt.

  • Quote rendering carries the saved price and scope attribution.

Document delivery
  • Artifact access is checked before the saved file is served.

  • The send workflow is separate from creating and approving the business document.

BRR budget review
  • A digest identifies the exact assessment used for a reviewed quotation.

  • Saved assessment terms preserve the package basis.

  • Client-report output is blocked until the wording approval is recorded.

REVIEW WITH YOUR TEAM

Does this match
the way you work?

Leave a workflow comment ↑