StockLive · Geelong Engineering workshop · delivery reference

The workflows and interfaces needed to turn a shared direction into a product.

A single inventory for leadership, product, design and engineering: what people need to do, where they enter, what must hand off, and which rules still need decisions.

← Workshop dashboard Leadership story deck
44Workflow surfaces
15System interfaces
10Decisions still required
The end-to-end product journey

One Lot, several clear handoffs.

Participant is the product-facing view. Sale Organisation is the backend relationship. The Lot remains the shared business record across the journey.

Current stageEnter with context
01 · ENTER

Sign in, choose context and connect a Participant.

Identity establishes who is acting. Organisation and Sale context determine what they can see and do.

02 · FORM

Create the Lot and complete its Declaration.

The Agent creates the central record directly in the Sale context, without an extra grouping workflow.

03 · ASSESS

Assign, capture, submit and review the Assessment.

Mobile entry, grid entry and import all converge on a reviewable handoff with an auditable correction loop.

04 · SELL

Offer the Lot through Auction or Catalog.

Auction, bidding, advertising and Buy Now use the same Lot while keeping their specialised behaviour separate.

05 · RECONCILE

Bring outcomes back with evidence.

External payloads, lifecycle history, failures and corrections remain traceable instead of disappearing into dashboard state.

01 · Participant and product workflows

Enter with the right context.

These interfaces establish identity, Sale and Organisation context before the work begins. Participant is the outward product term; Sale Organisation is the backend relationship.

Agreed directionRequired, details openSupporting capability
WF-01Agreed direction

Sign in

Purpose
Establish the real person acting.
Primary user
Every user.
Entry point
Application login.
Interface
Sign-in and account-recovery surfaces.
Exit / handoff
Authenticated identity passed to contextual authorization.
Status
Authentication grants no business access by itself.

Preview interface →

WF-02Agreed direction

Choose working context

Purpose
Make the active Organisation, Sale and capability visible.
Primary user
Agent, Assessor, Staff.
Entry point
After sign-in or context switch.
Interface
Organisation selector and persistent context indicator.
Exit / handoff
Scoped workspace and permitted actions.
Status
Uses role, permission and Organisation scope.

Preview interface →

WF-03Agreed direction

Personal workspace

Purpose
Show the work relevant to the current actor and context.
Primary user
Agent, Assessor, Reviewer.
Entry point
Authorised application landing.
Interface
Action cards, My Lots, My Assessments, Assigned to Me and Needs Review.
Exit / handoff
Direct entry into a permitted workflow.
Status
Composable and capability-led.

Preview interface →

WF-04Agreed direction

Find a Participant

Purpose
Identify the right business participant without duplicates.
Primary user
Agent or Staff.
Entry point
Sale workspace or Participant action.
Interface
Vendor phone and Property PIC search with match results.
Exit / handoff
Matched Organisation ready to connect to the Sale.
Status
PIC is unique; phone plus PIC supports discovery.

Preview interface →

WF-05Required, details open

Connect a Participant to a Sale

Purpose
Record that an Organisation is taking part.
Primary user
Agent or Staff.
Entry point
Matched Participant or Sale workspace.
Interface
Participation form, status and permission summary.
Exit / handoff
Sale Organisation relationship created or updated.
Status
The relationship name is settled; authorization meaning is open.

Preview interface →

WF-06Agreed direction

View a Sale workspace

Purpose
Provide the common context for Participants, Lots and outstanding work.
Primary user
Agent and Staff.
Entry point
Workspace, search or notification.
Interface
Sale overview, Participant list, Lot list, activity and actions.
Exit / handoff
Enter Participant, Lot, Auction or Catalog work.
Status
Sale remains the business source of truth during coexistence.

Preview interface →

WF-07Agreed direction

Create a Lot

Purpose
Create the central record for what will be offered.
Primary user
Agent.
Entry point
Sale workspace action card.
Interface
Lot form with livestock type and save-draft action.
Exit / handoff
Lot created and ready for Declaration and Assessment.
Status
Lot is the aggregate root.

Preview interface →

WF-08Agreed direction

Complete the Declaration

Purpose
Capture declaration data using the correct rules.
Primary user
Agent.
Entry point
New or existing Lot.
Interface
Versioned, configuration-driven Declaration form.
Exit / handoff
Declaration saved on the Lot.
Status
One Declaration and Declaration Config per Lot.

Preview interface →

WF-09Agreed direction

Assign an Assessor

Purpose
Make the next participant and responsibility explicit.
Primary user
Agent or Staff.
Entry point
Lot detail or creation completion.
Interface
Assessor search, assignment and reassignment control.
Exit / handoff
Assigned work and notification created.
Status
Lot and Assessment normally use a User owner.

Preview interface →

WF-10Agreed direction

View and manage a Lot

Purpose
Keep the full Lot story in one place.
Primary user
Authorised Participant or Staff.
Entry point
Search, workspace, activity or assignment.
Interface
Lot summary, Declaration, Assessment, state, Bids, history and actions.
Exit / handoff
Enter only actions granted in the current context.
Status
Lot is the common boundary across workflows.

Preview interface →

WF-11Supporting capability

Search, activity and notifications

Purpose
Help people return to work without rediscovery.
Primary user
Every authorised user.
Entry point
Global search, inbox or activity feed.
Interface
Search across Sale, Participant, Lot, PIC and external IDs; actionable notifications.
Exit / handoff
Open the scoped record or task.
Status
Must preserve Sale and Organisation context.

Preview interface →

02 · Assessment and review

A visible, auditable handoff loop.

The person who creates the Lot is not automatically the person who assesses it. Capability-led entry keeps responsibilities clear without forcing a fake role switch.

WF-12Agreed direction

Receive assigned work

Purpose
Give Assessors a focused entry to their work.
Primary user
Assessor.
Entry point
My Assessments, Assigned to Me or notification.
Interface
Queue with Sale, Lot, due state and assignment context.
Exit / handoff
Accept, return or open the Assessment.
Status
Assessor enters through participation, not Lot creation.

Preview interface →

WF-13Agreed direction

Capture an Assessment

Purpose
Record raw assessment input against the Lot.
Primary user
Assessor.
Entry point
Accepted assignment.
Interface
Mobile form, landscape grid and configuration-driven validation.
Exit / handoff
Draft Assessment retained for continued work.
Status
One Assessment belongs directly to the Lot.

Preview interface →

WF-14Agreed direction

Import Assessment data

Purpose
Bring structured external or spreadsheet data into the same workflow.
Primary user
Assessor or authorised Staff.
Entry point
Assessment capture.
Interface
CSV/XLSX upload, mapping preview, validation and error report.
Exit / handoff
Validated draft or explicit exceptions.
Status
Raw evidence must remain traceable.

Preview interface →

WF-15Agreed direction

Submit an Assessment

Purpose
Make completion and responsibility explicit.
Primary user
Assessor.
Entry point
Validated draft.
Interface
Completeness summary and submission confirmation.
Exit / handoff
Assessment enters Needs Review.
Status
Submission is auditable and reversible only through a recorded correction.

Preview interface →

WF-16Agreed direction

Review an Assessment

Purpose
Separate the maker from the reviewer.
Primary user
Reviewer or Manager.
Entry point
Needs Review queue.
Interface
Assessment, Lot context, validation results and decision actions.
Exit / handoff
Approve or request changes.
Status
Actor and reviewer remain distinct in history.

Preview interface →

WF-17Agreed direction

Request corrections

Purpose
Return incomplete work with a clear reason.
Primary user
Reviewer.
Entry point
Review decision.
Interface
Reason entry, correction note and return action.
Exit / handoff
Work returns to the Assessor queue.
Status
Reason, actor and time are part of the audit record.

Preview interface →

WF-18Agreed direction

Approve and continue

Purpose
Confirm that the Assessment is ready for the next business step.
Primary user
Reviewer.
Entry point
Review decision.
Interface
Approval confirmation and next-state guidance.
Exit / handoff
Lot becomes ready for sale preparation.
Status
Exact Lot/Auction state allocation remains open.

Preview interface →

03 · Auction, Catalog and Bid

One Lot, two selling paths.

Auction is the selling event inside Exchange. Catalog is a separate Sale subtype with its own routes, indexes and actions. Bids attach directly to the Lot.

WF-19Agreed direction

Derive an Auction

Purpose
Create the Exchange event without creating competing truth.
Primary user
Authorised Staff.
Entry point
Existing Sale.
Interface
Auction setup with visible Sale compatibility state.
Exit / handoff
Auction references or projects the authoritative Sale.
Status
Sale remains business source of truth during coexistence.

Preview interface →

WF-20Required, details open

Add Lots to an Auction

Purpose
Associate sale-ready Lots with the event.
Primary user
Agent or Staff.
Entry point
Auction workspace.
Interface
Lot selection, ordering and AuctionLot settings.
Exit / handoff
Lots ready for provider validation.
Status
AuctionLot-specific state split remains open.

Preview interface →

WF-21Agreed direction

Prepare Lots for Nexlot

Purpose
Prevent incomplete outbound data from becoming silent failure.
Primary user
Agent or Staff.
Entry point
Auction Lot readiness action.
Interface
Readiness checklist, validation details and send command.
Exit / handoff
Valid Lots sent; exceptions held for resolution.
Status
Nexlot connects directly to Lot/AuctionLot.

Preview interface →

WF-22Supporting capability

Monitor an Auction

Purpose
Show event, Lot and integration health in one operational view.
Primary user
Staff and authorised Agents.
Entry point
Auction workspace.
Interface
Lot states, provider status, exceptions and activity.
Exit / handoff
Open a Lot, bidder, failure or reconciliation task.
Status
Dashboard state must not replace business state.

Preview interface →

WF-23Supporting capability

Manage bidders

Purpose
Keep bidder identity and event participation usable.
Primary user
Staff.
Entry point
Auction or bidder administration.
Interface
Registration search, link/repair and export.
Exit / handoff
Bidder identity available for Bid reconciliation.
Status
External identity must remain traceable.

Preview interface →

WF-24Required, details open

View Bid history

Purpose
Explain offers made against a Lot.
Primary user
Authorised Participant or Staff.
Entry point
Lot or Auction detail.
Interface
Bidder, amount, time, order, status, source and leading/winning state.
Exit / handoff
Outcome or reconciliation investigation.
Status
Target ownership is clear; detailed backfill evidence is open.

Preview interface →

WF-25Required, details open

Close and reconcile bidding

Purpose
Bring provider outcomes back into trusted Lot state.
Primary user
Staff.
Entry point
Auction close or provider result.
Interface
Winning outcome, sold/unsold state, mismatch and replay controls.
Exit / handoff
Reconciled result with retained evidence.
Status
Payload, ordering and status contract remain open.

Preview interface →

WF-26Agreed direction

Manage a Catalog

Purpose
Create and control the separate Catalog selling area.
Primary user
Authorised User or Organisation representative.
Entry point
Catalog workspace.
Interface
Draft, Published and Archived lifecycle; owner, dates and type.
Exit / handoff
Catalog ready for discovery or integration.
Status
Catalog is a standalone Sale subtype.

Preview interface →

WF-27Agreed direction

Browse and search Catalogs

Purpose
Let buyers discover current offerings.
Primary user
Buyer or Participant.
Entry point
Catalog index.
Interface
Standalone Catalog routes, search, filters and status-aware results.
Exit / handoff
Open a Catalog or Lot detail.
Status
Catalog is not indexed as Auction.

Preview interface →

WF-28Agreed direction

View a Catalog Lot

Purpose
Present the Lot and commercial context to a buyer.
Primary user
Buyer or Participant.
Entry point
Catalog results.
Interface
Lot description, media, summary, timing and available action.
Exit / handoff
Advertising response, Buy Now or external action.
Status
The Lot remains the offered record.

Preview interface →

WF-29Agreed direction

Advertise a Lot

Purpose
Publish a non-bidding Catalog offering.
Primary user
Catalog owner.
Entry point
Catalog Lot action.
Interface
Advertising controls, publication state and contact path.
Exit / handoff
Visible offering or recorded enquiry.
Status
Advertising is Catalog-specific behaviour.

Preview interface →

WF-30Required, details open

Buy Now

Purpose
Allow an immediate purchase path where configured.
Primary user
Buyer.
Entry point
Eligible Catalog or Auction Lot.
Interface
Offer, confirmation, eligibility and outcome states.
Exit / handoff
Confirmed transaction or clear failure.
Status
Named by the workshop; commercial rules were not captured.

Preview interface →

WF-31Required, details open

Operate Catalog integration

Purpose
Connect Catalog offerings to configured external channels.
Primary user
Staff or Catalog owner.
Entry point
Catalog integration settings.
Interface
Provider selection, sync state, errors and retry.
Exit / handoff
Published external state or actionable exception.
Status
Provider and ownership contract need design evidence.

Preview interface →

04 · Internal Manage workflows

The operational system behind the visible journey.

Manage is the internal shell for Staff and Super Admin. It hosts registered engines and operational workflows without taking ownership of every domain.

WF-32Agreed direction

Use the Manage dashboard

Purpose
Give internal users one entry to registered engines.
Primary user
Staff and Super Admin.
Entry point
Manage login.
Interface
Engine navigation, highlights and operational queues.
Exit / handoff
Open the owning engine's workflow.
Status
Manage is shell and host, not universal domain owner.

Preview interface →

WF-33Supporting capability

Administer engine access

Purpose
Control which internal modules each Staff member can use.
Primary user
Super Admin.
Entry point
Manage administration.
Interface
Staff access matrix across registered engines.
Exit / handoff
Updated internal access policy.
Status
Internal roles are relatively static.

Preview interface →

WF-34Agreed direction

Act for an Agent

Purpose
Let Staff perform authorised work without losing true identity.
Primary user
Staff.
Entry point
Scoped Agent selector.
Interface
Prominent “acting as” state, reason/context and exit action.
Exit / handoff
Action executes with both identities recorded.
Status
Actual and represented actors must remain visible.

Preview interface →

WF-35Supporting capability

Inspect contextual audit

Purpose
Explain who did what, for whom and where.
Primary user
Staff, reviewer or support.
Entry point
Lot, Sale, Participant or activity history.
Interface
Filterable actor, represented actor, action, time, Sale and Organisation timeline.
Exit / handoff
Resolved question or linked investigation.
Status
Append-only evidence is required.

Preview interface →

WF-36Supporting capability

Work cross-Organisation queues

Purpose
Let internal teams triage work without losing scope.
Primary user
Staff.
Entry point
Manage highlights or queues.
Interface
Filterable pending reviews, assignments, failures and active Sales.
Exit / handoff
Open the record with explicit context.
Status
Every action rechecks Organisation and Sale scope.

Preview interface →

WF-37Supporting capability

Configure livestock types

Purpose
Choose which Assessment and Declaration rules apply.
Primary user
Authorised administrator.
Entry point
Configuration administration.
Interface
Livestock Type Config index, detail and version associations.
Exit / handoff
Config selection available to a Lot.
Status
Both config families belong independently to livestock type.

Preview interface →

WF-38Required, details open

Version Assessment Config

Purpose
Evolve capture rules without breaking historical interpretation.
Primary user
Authorised administrator.
Entry point
Assessment Config administration.
Interface
Editor, preview, validation, version and activation controls.
Exit / handoff
Immutable version selectable by new Lots.
Status
Version-selection and retention rules need definition.

Preview interface →

WF-39Required, details open

Version Declaration Config

Purpose
Evolve declaration rules while retaining historical meaning.
Primary user
Authorised administrator.
Entry point
Declaration Config administration.
Interface
Editor, preview, validation, version and activation controls.
Exit / handoff
Immutable version selectable by new Lots.
Status
Version-selection and retention rules need definition.

Preview interface →

WF-40Required, details open

Configure providers

Purpose
Define how Integration, Import and Internal configurations behave.
Primary user
Authorised administrator.
Entry point
Config type or integration settings.
Interface
Provider/reference selection and adapter settings.
Exit / handoff
Valid provider configuration available to capture/import.
Status
Eyefillet, Agrinous, Frisbee and Optiweigh representation is unresolved.

Preview interface →

WF-41Supporting capability

Resolve quarantined records

Purpose
Keep incomplete provider data explicit and recoverable.
Primary user
Operations or support Staff.
Entry point
Exception queue or failed import.
Interface
Raw payload, reason, missing mappings, repair and replay.
Exit / handoff
Attached domain record or documented rejection.
Status
Incomplete records must never silently corrupt a Lot.

Preview interface →

WF-42Required, details open

Reconcile Sale and Auction

Purpose
Detect divergence during migration.
Primary user
Operations or engineering Staff.
Entry point
Migration dashboard or mismatch alert.
Interface
Side-by-side identifiers, state, source and repair action.
Exit / handoff
Restored single source of business truth.
Status
Detailed compatibility and repair contract remain open.

Preview interface →

WF-43Supporting capability

Investigate Bid identity

Purpose
Resolve missing or conflicting bidder and Bid mappings.
Primary user
Support or operations Staff.
Entry point
Bid exception or reconciliation view.
Interface
External IDs, bidder linkage, raw evidence and resolution action.
Exit / handoff
Resolved mapping or explicit unresolved identity.
Status
Stable source identity is mandatory.

Preview interface →

WF-44Required, details open

Investigate production behaviour

Purpose
Help another engineer understand failure without relying on one person.
Primary user
Engineering and operations.
Entry point
Error, alert or user report.
Interface
Errors, logs, metrics, traces, deploys, runbooks and linked business context.
Exit / handoff
Diagnosis, rollback, repair or incident action.
Status
Workshop did not assess current operational coverage.

Preview interface →

05 · System and integration interfaces

The boundaries that keep truth intact.

These are contracts, not screens. Each boundary needs a producer, consumer, evidence, failure behaviour and an explicit maturity state.

IF-01

Frontend → backend API

Producer
Platform / CTP frontend.
Consumer
Backend API and owning engines.
Crosses boundary
Context, queries, commands and workflow responses.
Evidence
Stable API contract with Sale and Organisation context.
Failure handling
Actionable validation and unavailable-service states.
Status
Required, details open — API/CES ownership is unresolved.
IF-02

Identity → contextual authorization

Producer
Authenticated identity and current context.
Consumer
Every protected workflow action and view.
Crosses boundary
Actor, represented actor, role, permission, Organisation, Sale and action.
Evidence
Permify decision plus recorded context.
Failure handling
Denied actions explain missing scope without leaking data.
Status
Agreed direction — detailed policy model remains to be written.
IF-03

HubSpot → StockLive

Producer
HubSpot sales-lead and Organisation management.
Consumer
StockLive Participant/Sale workflows.
Crosses boundary
Intent, Organisation identity and management changes.
Evidence
Stable external identity and source timestamps.
Failure handling
Retry, mismatch and manual reconciliation.
Status
Agreed direction — failure/reconciliation behaviour is open.
IF-04

Legacy Sale → Exchange Auction

Producer
Legacy Sale, the coexistence source of business truth.
Consumer
Exchange Auction projection or reference.
Crosses boundary
Event identity and compatible business state.
Evidence
Reference/projection with explicit source.
Failure handling
Divergence detection; no uncontrolled dual writes.
Status
Agreed direction — detailed compatibility contract is open.
IF-05

Exchange → Nexlot

Producer
Exchange Lot and AuctionLot.
Consumer
Nexlot provider.
Crosses boundary
Sale/Auction identity, Lot data and offering context.
Evidence
Stable external keys and retained outbound payload.
Failure handling
Validation, explicit failure, retry and reconciliation.
Status
Agreed direction — field-level contract needs evidence.
IF-06

Nexlot → Exchange

Producer
Nexlot results and Bid data.
Consumer
Exchange Auction/Lot/Bid workflows.
Crosses boundary
External identities, bidder, amount, currency, time, order and status.
Evidence
Original payload and import metadata.
Failure handling
Quarantine incomplete identity/target/value evidence.
Status
Required, details open — complete payload contract is missing.
IF-07

Provider payload → staging and quarantine

Producer
Any external import or provider adapter.
Consumer
Validated domain attachment.
Crosses boundary
Raw payload, stable import key, mapping state and reason.
Evidence
Replayable source plus deterministic identity.
Failure handling
Hold incomplete records; allow repair and replay.
Status
Supporting capability — required by the integration direction.
IF-08

CSV/XLSX → Assessment

Producer
User-supplied structured file.
Consumer
Assessment capture workflow.
Crosses boundary
Rows, fields, source metadata and mapping choices.
Evidence
Preview, validation results and retained import record.
Failure handling
Row-level errors without losing accepted data or source.
Status
Agreed direction — field mappings depend on config.
IF-09

Provider adapters → Assessment Config

Producer
Eyefillet, Agrinous, Frisbee, Optiweigh or future adapters.
Consumer
Configuration-driven Assessment intake.
Crosses boundary
Provider identity, fields and mapping version.
Evidence
Adapter reference and immutable config version.
Failure handling
Unsupported provider/version becomes an explicit exception.
Status
Required, details open — provider representation is unresolved.
IF-10

Raw Assessment → Lot summary

Producer
Validated Assessment and selected config.
Consumer
Structured Assessment Summary on Lot.
Crosses boundary
Configuration-aware summarised JSON.
Evidence
Source Assessment ID and config version.
Failure handling
Mapping failure retains raw input and blocks false completion.
Status
Agreed direction — exact HTML/data mapping is open.
IF-11

Engines → Manage registry and highlights

Producer
Registered sibling engines and their jobs.
Consumer
Manage navigation and highlights view.
Crosses boundary
Registration metadata, permitted access and summary counts.
Evidence
Engine-owned update job and timestamp.
Failure handling
Stale highlight is marked; engine removal does not break Manage.
Status
Supporting capability — module contract is not fully defined.
IF-12

Domain changes → audit history

Producer
Lot, Auction and contextual workflow actions.
Consumer
PaperTrail/Jira evidence and history views.
Crosses boundary
Before/after state, actor, represented actor, time and context.
Evidence
Append-only version and decision trail.
Failure handling
Audit failure must not silently erase accountability.
Status
Agreed direction — exact event model needs normalisation.
IF-13

Workflow events → notifications

Producer
Assignment, correction, approval and integration events.
Consumer
User inbox and external notification channels.
Crosses boundary
Recipient, scoped record, reason and next action.
Evidence
Delivery attempt and source event.
Failure handling
Retry and visible undelivered state without duplicating action.
Status
Supporting capability — channel rules were not defined.
IF-14

Applications → operational telemetry

Producer
Frontend, backend, jobs and integrations.
Consumer
Errors, logs, metrics, traces and alerts.
Crosses boundary
Technical signal with safe business identifiers and deploy context.
Evidence
Correlated request/job/import identity.
Failure handling
Actionable alert, runbook and owner.
Status
Required, details open — current coverage was not assessed.
IF-15

Content/CES → frontend

Producer
Content editing or CES/API capability.
Consumer
Frontend options, landing and presentation surfaces.
Crosses boundary
Managed content and presentation configuration.
Evidence
Versioned contract and ownership boundary.
Failure handling
Safe fallback content and visible unavailable state.
Status
Required, details open — meaning and ownership of CES are unresolved.
06 · Explicit exclusions

Interfaces the target model does not need.

These names appear here only to make the boundary explicit. They are historical concepts, not target workflow cards or new product surfaces.

No Consignment workflow

Grouping previously associated with Consignment is handled through Lot or Sale context; it does not require a standalone screen or entity.

No Listing editor or model

The Lot is the record being offered. AuctionLot carries event association where needed.

No standalone Item workflow

Item was not justified as a target entity in the final capability set.

No duplicate StockLive Booking CRUD

HubSpot owns sales-lead intent and Organisation creation/management.

No forced role switch

Users with several capabilities see permitted actions in one context-aware workspace.

No second Auction truth

Exchange Auction may mirror or project Sale during coexistence; it must not become a competing source.

07 · Decisions still required

Open rules, not hidden assumptions.

The existence of a workflow does not mean every business rule is known. These decisions should be closed before detailed design or implementation relies on them.

D-01 · PRODUCT RULE

Participant authorization

Define what a Participant may see or do through the Sale Organisation relationship.

D-02 · DOMAIN STATE

Lot, Auction and AuctionLot states

Allocate authoritative lifecycle states and transition history without letting dashboard state become business truth.

D-03 · OWNERSHIP

Workflow ownership

Name the owning engine and API for Lot, Assessment, Auction, Catalog and Bid workflows.

D-04 · ARCHITECTURE

Frontend, backend and CES boundary

Normalise Platform/CTP, CDB, Manage, frontend, API and CES responsibilities.

D-05 · COMMERCIAL RULE

Buy Now

Define eligibility, pricing, confirmation, competition with bidding and final outcome behaviour.

D-06 · INTEGRATION EVIDENCE

Complete Bid contract

Prove stable identity, target, bidder, amount, currency, time, sequence, status and reconciliation data.

D-07 · PRODUCT RULE

Catalog ownership and types

Define ownership and the precise meaning of Advertising, Buy and Auction Catalog types.

D-08 · CONFIGURATION

Config versions and providers

Define how Lots retain versions and how integration providers are represented.

D-09 · INTEGRATION OPERATIONS

HubSpot reconciliation

Define retry, conflict and manual-resolution behaviour for Participant and Organisation changes.

D-10 · OPERATIONS

Production observability

Assess current errors, logs, metrics, tracing, alerts, deployments, rollback and incident ownership.

Authority and scope. This inventory uses the final Day 4 synthesis and technical capability map as authority, with the role/capability prototype supplying interface detail where consistent. It is a planning reference—not a final permission policy, database schema or delivery commitment.