Map
Define the current workflow, evidence, owner and operating constraint.
OPERATING SINCE2006LETTERBOX COVERAGESYDNEYDIGITAL SERVICEAU + NZENQUIRY REVIEWSENIOR TEAMCALL TRACKING PLATFORMISO 27001 CERTIFIEDOPERATING SINCE2006LETTERBOX COVERAGESYDNEYDIGITAL SERVICEAU + NZENQUIRY REVIEWSENIOR TEAMCALL TRACKING PLATFORMISO 27001 CERTIFIED
GibsonLetterbox · Call Tracking · Revenue Recovery · Sydney since 2006
Public evidence pending
Learning Sphere
A training-platform build pattern involving cohort, assessment and progress workflows. It remains a Sandbox record while permissioned public evidence, operating status and limitations are reconciled.
Last reviewed 2 August 2026 · By Albert Triolo, Founder and Managing Director
Current public statusPrototype claim under evidence review
What the evidence shows
Build time, scale, cost, assessment quality and production status are not published as verified outcomes on this page.
What is confirmed
Facts this entry can support.
- 01The problem concerns a multi-step training and assessment workflow.
- 02The public record is not being presented as a production case study.
- 03Any future customer scope begins with existing systems, users, controls and evidence requirements.
How a similar problem proceeds
Evidence to decision, without assuming AI is the answer.
Compare
Check process, rule, integration and AI options against the same decision.
Bound
Set representative cases, human controls, unacceptable failures and stop conditions.
Decide
Stop, improve, test further or separately scope production from the evidence.
Questions before using this example
Status and fit, answered directly.
What is the current public status of Learning Sphere?
Prototype claim under evidence review. Build time, scale, cost, assessment quality and production status are not published as verified outcomes on this page.
What does Learning Sphere show?
A training-platform build pattern involving cohort, assessment and progress workflows. It remains a Sandbox record while permissioned public evidence, operating status and limitations are reconciled.
Can this example predict the outcome of another build?
No. A future workflow has its own evidence, systems, users, risks, human controls, acceptance tests and production decision. This entry supports a capability discussion only within the stated limits of the evidence.
What information should go into a workflow brief?
Describe the current process, the constraint, affected users, systems involved, available evidence, unacceptable failures, required human decisions and the outcome that would justify a bounded test.
Next decision
Do not copy the example. Scope the operating problem.
Review the Automation & AI method, then send the current process, evidence and controls if a bounded workflow decision is still useful.