Stage P1 · Revision 2
Public foundation
Current Talomnia materials describe the launch as internal product use before commercial validation. This provides an inspectable starting point; it does not establish external demand or a completed commercial launch. Next: review the published workflows and evidence; contact the team to discuss a specific work problem.
- Development state
- building
- Commercial availability
- unavailable
- Evidence state
- internal
- Target window
- No target window is stated
Intended outcome
Maintain a public starting point that shows product status, limits, and available evidence.
Limitations
This stage does not announce commercial availability. This record contains no accepted external paid case; commercial availability remains unavailable in every mode.
Availability by mode
- Customer-owned — Talomnia Workforce: unavailable
- Managed by Talomnia — Talomnia Workforce: unavailable
- Self-hosted — Talomnia Workforce: unavailable
Conditions and checks
-
Publish the current bilingual stage page with its source, limitations, and working evidence links; verify the exact release version.
Evidence required: The five-stage source and rendered bilingual page at the same revision.; A release check identifying the exact deployed site version.
Check decision: not evaluated
Stage P2 · Revision 2
First external case
Planned stage: test one bounded professional-work case with an external customer and retain the result with acceptance evidence. An interested organization can contact the team to discuss the task and its scope; this is an invitation to talk, not an offer or confirmation that a service is available.
- Development state
- planned
- Commercial availability
- unavailable
- Evidence state
- unestablished
- Target window
- No target window is stated
Intended outcome
Record the first completed external paid case with evidence of the result and acceptance.
Limitations
This stage is planned and is not represented as started or passed by this record. Payment, credit, and refund terms are not announced here; customer-owned, managed, and self-hosted modes are unavailable.
Availability by mode
- Customer-owned — Talomnia Workforce: unavailable
- Managed by Talomnia — Talomnia Workforce: unavailable
- Self-hosted — Talomnia Workforce: unavailable
Conditions and checks
-
Complete the first external paid case and publish evidence of its result and acceptance.
Evidence required: A public case record that identifies the agreed scope and the accepted result.; A verified record that the case was paid under published terms.
Check decision: not evaluated
Stage P3 · Revision 2
Repeatable delivery
Planned stage: test whether accepted work can be repeated across a series of external cases rather than a single example. Talomnia's next step is to publish how acceptance and costs are measured before drawing conclusions about repeatability. If you have a suitable repeat-use case, contact the team to discuss what evidence would be needed; this does not imply that a service is available.
- Development state
- planned
- Commercial availability
- unavailable
- Evidence state
- unestablished
- Target window
- No target window is stated
Intended outcome
Achieve a series of paid cases with positive acceptance and measured gross margin that includes human review.
Limitations
Repeatability, reuse economics, and gross margin are stated as goals, not measured results. This stage remains planned until the preceding gate is met; commercial modes are unavailable.
Availability by mode
- Customer-owned — Talomnia Workforce: unavailable
- Managed by Talomnia — Talomnia Workforce: unavailable
- Self-hosted — Talomnia Workforce: unavailable
Conditions and checks
-
Verify a series of paid cases with positive acceptance and measured gross margin using a published method.
Evidence required: A dated series of external case and acceptance records.; A reproducible gross-margin calculation that includes measured human review.
Check decision: not evaluated
Stage P4 · Revision 2
Early scale
Planned stage: expand volume only after repeatability is evidenced and operating capacity and limits are measured. The next step is to publish a bounded scaling plan with its measurement sources; a calendar date alone does not open this stage. Contact the team to discuss the evidence needed for future scaling; this makes no promise about volume or timing.
- Development state
- planned
- Commercial availability
- unavailable
- Evidence state
- unestablished
- Target window
- No target window is stated
Intended outcome
Show a measured operating range and its limits before expanding volume or availability.
Limitations
This record does not establish scale, capacity, timelines, or availability to organizations. It implies no volume commitment, SLA, or commercial readiness.
Availability by mode
- Customer-owned — Talomnia Workforce: unavailable
- Managed by Talomnia — Talomnia Workforce: unavailable
- Self-hosted — Talomnia Workforce: unavailable
Conditions and checks
-
Before opening this stage, publish a bounded capacity and measurement plan grounded in evidenced repeatability.
Evidence required: A versioned operating-range proposal with named measurement sources and limits.; Evidence that the preceding repeatability gate remains satisfied.
Check decision: not evaluated
Stage P5 · Revision 2
Infrastructure layers
Planned stage: add infrastructure capabilities only after execution in the preceding stages is evidenced. The next step is to publish each proposed capability's scope, measurements, operating requirements, and rollback path in advance. Contact the team to discuss published limits and evidence; this plan does not mean infrastructure modes are available.
- Development state
- planned
- Commercial availability
- unavailable
- Evidence state
- unestablished
- Target window
- No target window is stated
Intended outcome
Develop infrastructure incrementally while retaining verifiable limits and evidence from earlier stages.
Limitations
Infrastructure layers here are a plan, not a claim about an available product. Specific capabilities, timelines, service levels, and usage modes are not established.
Availability by mode
- Customer-owned — Talomnia Workforce: unavailable
- Managed by Talomnia — Talomnia Workforce: unavailable
- Self-hosted — Talomnia Workforce: unavailable
Conditions and checks
-
Before opening this stage, publish the specific capability, its limits, evidence source, operating conditions, and rollback path.
Evidence required: A versioned capability proposal with an explicit evidence and operational boundary.; Evidence that the preceding scale gate remains satisfied.
Check decision: not evaluated