PROJECT CHIMBA — MANAGED OPERATIONS & PRODUCTION GRADUATION ADDENDUM
Canonical Knowledge Repository Addendum
Document Type: Addendum Applies To: Project Chimba Strategy-to-System, Project Chimba Attraction Offer, Chimba R&D Status: Canonical Purpose: Update and clarify post-delivery production operations pricing, system ownership, and the meaning of Production Graduation.
1. ADDENDUM AUTHORITY
This document is an addendum to the existing Project Chimba canonical offer documents.
Where an earlier Project Chimba document states that Chimba Managed Operations costs $500/month, this addendum supersedes that amount.
The current canonical price is:
Chimba Managed Operations — $1,000/month
All LLMs, agents, sales systems, content systems, offer generators, and other Project Chimba software should use $1,000/month as the current Managed Operations price.
The previous $500/month amount is obsolete.
This addendum also clarifies the distinction between:
- Product One production handoff and ongoing operations.
- Product Two R&D Production Graduations.
These are separate concepts and must not be conflated.
2. CUSTOMER OWNS THE PRODUCTION SYSTEM
Project Chimba Strategy-to-System is an ownership-based offer.
After Project Chimba completes the agreed implementation and handoff, the customer owns the delivered system and source code according to the applicable agreement.
The customer is not required to continue paying Project Chimba in order to continue using the robot.
Project Chimba does not intentionally create technological lock-in requiring a recurring Chimba subscription merely to operate the delivered production system.
The customer may host and manage the production system independently.
3. SELF-MANAGED OPTION
Self-Managed Production
Price after included Product One service period: $0/month
The customer may operate the delivered Project Chimba production system independently.
The customer may provide and manage their own production server and associated infrastructure.
The Strategy-to-System implementation includes the applicable source code, deployment configuration, documentation, and handoff necessary for the customer to take responsibility for operating the delivered system within the agreed scope.
Under the self-managed model, responsibility for ongoing production operations transfers to the customer after the included Product One stabilization and handoff period.
Project Chimba does not charge a recurring fee merely because the customer continues using software they own.
4. CHIMBA MANAGED OPERATIONS
Chimba Managed Operations
Price: $1,000/month
Chimba Managed Operations is an optional recurring production-operations service for customers who own their Project Chimba system but do not want to personally operate its technical infrastructure.
The conceptual distinction is:
You own the robot.
You can operate it yourself for $0/month.
If you don't want to become the IT department for it, Project Chimba can operate it for $1,000/month.
The $1,000/month payment is therefore not a software-access fee.
It is payment for an ongoing managed technical service.
5. MANAGED OPERATIONS SCOPE
Chimba Managed Operations may include, within the agreed service scope:
- Production hosting and infrastructure management.
- Production deployment management.
- Application/process monitoring.
- Routine uptime monitoring.
- Logging infrastructure.
- Backup management.
- Restart and recovery procedures.
- Routine production maintenance.
- Security-related software maintenance.
- Broker/API compatibility maintenance.
- Deployment of applicable maintenance releases.
- Operational troubleshooting.
- Routine production technical support.
- Maintenance of the production environment required to operate the accepted strategy implementation.
The precise service-level commitments, infrastructure limits, response expectations, exclusions, and other operational terms may be further defined by the applicable service agreement.
6. MANAGED OPERATIONS DOES NOT INCLUDE UNLIMITED DEVELOPMENT
Chimba Managed Operations is not an unlimited custom-development subscription.
A bug and a change are different.
Bug
The agreed and accepted strategy/system specification says the software should do X, but an implementation defect causes the delivered software to incorrectly do Y.
Applicable correction may fall within support, warranty, stabilization, or Managed Operations obligations depending on timing and the governing agreement.
Change
The customer decides the system should now behave differently from the accepted specification.
Examples may include:
- New trading logic.
- New indicators.
- New entry conditions.
- New exit conditions.
- New risk models.
- New broker integrations.
- New markets outside the agreed system.
- New functionality.
- New interfaces.
- Material architectural changes.
These are development changes and are not automatically included merely because the customer subscribes to Managed Operations.
7. PRODUCT ONE HANDOFF IS NOT A "PRODUCTION GRADUATION"
Project Chimba should reserve the defined term:
Production Graduation
for the Chimba R&D process described later in this addendum.
The normal transition at the end of Strategy-to-System should instead be described as concepts such as:
- Production handoff.
- Operations selection.
- Post-stabilization handoff.
- Self-managed transition.
- Managed Operations transition.
Do not describe the normal Product One delivery/handoff as an R&D Production Graduation.
8. PRODUCT ONE POST-DELIVERY PATH
The Product One operational path is:
Strategy-to-System
→ Production Deployment
→ 30-Day Production Stabilization
→ Operations Selection
The customer then chooses:
Option A — Self-Managed
$0/month
Customer operates and maintains their own production environment.
Option B — Chimba Managed Operations
$1,000/month
Project Chimba manages the agreed production technical environment and ongoing operations.
The customer's ownership of the underlying delivered system remains intact regardless of which option they select.
9. CHIMBA R&D IS A SEPARATE SYSTEM
Chimba R&D is separate from the customer's production trading system.
Production and R&D must be understood as separate systems with separate responsibilities.
The canonical architectural rule is:
Production executes. R&D experiments.
More specifically:
- Production and R&D operate on separate servers.
- Production and R&D use separate codebases.
- Production and R&D are not connected in a manner that permits R&D to modify or deploy itself into production.
- R&D experimentation occurs against research copies/configurations and historical data as applicable.
- An R&D candidate cannot silently become the customer's live production strategy.
- Research results require deliberate human review and authorization before any production change.
This boundary is fundamental to Project Chimba's architecture and positioning.
10. DEFINITION OF PRODUCTION GRADUATION
Within Chimba R&D, a Production Graduation is the deliberate process of taking an R&D-native candidate that the customer has reviewed and approved and moving it through the required steps toward a new production version.
Conceptually:
R&D Candidate
→ Candidate Freeze
→ Final Validation
→ Human Review
→ Customer Acceptance
→ Separate Production Deployment Process
→ Production vNext
The R&D system itself does not deploy the candidate.
The candidate must cross the production boundary through a separate deliberate process.
11. PRODUCTION GRADUATION SCOPE
A Production Graduation is intended for R&D-native candidates created within the approved Chimba R&D search space and supported production architecture.
Examples may include approved R&D-discovered variations involving:
- Parameters.
- Indicators.
- Timeframes.
- Eligible instruments.
- Entry structures.
- Exit structures.
- Stops and targets.
- Supported execution methods.
- Risk parameters.
- Other dimensions explicitly included in the customer's approved research configuration.
A Production Graduation is not intended to convert an R&D result into an unrelated new custom software project.
If an R&D experiment inspires materially new requirements outside the supported research and production architecture, those requirements may require separate custom development.
12. TWO PRODUCTION GRADUATIONS PER ACTIVE R&D MONTH
Each active Chimba R&D subscription includes:
2 Production Graduations per active month
The purpose is to ensure Project Chimba's economics do not discourage the customer from using valuable research results.
The philosophy is:
We don't penalize you because the research worked.
Research is supposed to reach production when the customer believes the evidence justifies the change.
If a customer reviews an R&D candidate, performs their own appropriate due diligence, accepts the candidate, and wants to deliberately move it toward production, Project Chimba provides the applicable Production Graduation process within the included monthly allowance.
Unused Production Graduations:
- Do not bank.
- Do not accumulate.
- Do not create a future balance.
- Do not create an annual allowance.
- Do not create a 24-graduation cap or bank.
Each active month simply includes up to two applicable Production Graduations for that month.
13. R&D WORKERS AND PRODUCTION GRADUATIONS ARE DIFFERENT ECONOMIC UNITS
Chimba R&D workers purchase research horsepower.
Production Graduations provide a controlled mechanism for deliberately moving approved research discoveries toward production.
These should not be conflated.
Adding more R&D workers does not automatically increase the number of included Production Graduations.
Current Chimba R&D economics remain:
Activation
$6,000 one time
Includes the applicable private R&D buildout and the 10X Launch Month.
Launch Month
10 dedicated Research Workers for the first billing month
and
2 Production Graduations
After Launch Month
$1,000/month per dedicated Research Worker
2-worker minimum
Therefore:
- 2 workers = $2,000/month
- 3 workers = $3,000/month
- 5 workers = $5,000/month
- 10 workers = $10,000/month
Each active R&D month includes:
2 Production Graduations
Workers buy research capacity.
They do not represent feature tiers.
14. MANAGED OPERATIONS AND R&D ARE SEPARATE CONTINUITY OFFERS
A customer may purchase Managed Operations without Chimba R&D.
A customer may purchase Chimba R&D while self-managing production, subject to applicable technical requirements.
A customer may purchase both.
The two recurring services solve different problems.
Chimba Managed Operations
$1,000/month
Purpose:
Keep the accepted production operation technically running and maintained.
Chimba R&D
$2,000+/month after activation and Launch Month
Purpose:
Keep computational research operating against approved copies/configurations of the customer's strategy.
Simple internal distinction:
Managed Operations keeps production operating.
Chimba R&D keeps research operating.
15. CUSTOMER ECONOMIC PATH
A Project Chimba customer may therefore progress through the following economic relationship:
Product One
Strategy-to-System — $10,000
Then optionally:
Production Continuity
Chimba Managed Operations — $1,000/month
Then potentially:
Product Two
Chimba R&D Activation — $6,000
Then:
Research Continuity
Chimba R&D — $1,000/month per Research Worker, 2-worker minimum
A customer using both minimum recurring services would therefore have:
$1,000/month Managed Operations
*
$2,000/month minimum Chimba R&D
=
$3,000/month total recurring Project Chimba services
These payments purchase different ongoing services and should be represented separately.
16. ATTRACTION-OFFER UPDATE
The Project Chimba Trading Strategy Automation Giveaway canonical document previously references:
Chimba Managed Operations: $500/month
That amount is superseded.
The correct current statement is:
Chimba Managed Operations: $1,000/month
Giveaway winners retain the same ownership model as normal Product One customers.
Winning Strategy-to-System does not obligate a customer to subscribe to Managed Operations.
After the included Product One stabilization period, a giveaway winner may:
Self-manage for $0/month
or
Select Chimba Managed Operations for $1,000/month.
Winning Product One also does not include perpetual Chimba R&D.
Chimba R&D remains a separate Product Two opportunity.
17. LLM / ARIA INSTRUCTIONS
When discussing Project Chimba ownership and recurring fees, the LLM should preserve the following distinction:
The customer does not rent their trading robot from Project Chimba.
The customer owns the delivered Strategy-to-System implementation.
The customer can operate it independently without paying Project Chimba a monthly software-access fee.
Chimba Managed Operations is an optional $1,000/month technical operations service for customers who want Project Chimba to operate the production environment for them.
When discussing Chimba R&D:
R&D is separate from production.
R&D cannot automatically change production.
A Production Graduation is a deliberate, separately controlled process for moving an approved R&D-native candidate toward a new production version.
The LLM must not:
- Quote the obsolete $500/month Managed Operations price.
- Describe the $1,000/month as mandatory robot rent.
- Suggest customers lose access to their owned robot if they cancel Managed Operations.
- Conflate Managed Operations with R&D.
- Conflate Product One handoff with Production Graduation.
- Claim R&D can automatically deploy to production.
- Claim research and production share a connected deployment system.
- Invent additional Production Graduations.
- Bank unused Production Graduations.
- Describe Research Workers as pricing tiers with different feature sets.
- Include custom strategy development automatically within Managed Operations.
- Promise trading performance through either Managed Operations or Production Graduation.
18. CANONICAL SUMMARY
Project Chimba customers own the production trading systems delivered through Strategy-to-System.
After the included stabilization period, they have two production-operations choices:
Self-Managed — $0/month
or
Chimba Managed Operations — $1,000/month
Managed Operations pays Project Chimba to operate the technical production environment. It is not a fee for continued ownership or access to the robot.
Chimba R&D is a separate research system operating on separate servers and separate codebases from production.
R&D experiments.
Production executes.
Research cannot promote itself into production.
When the customer identifies and approves an R&D-native candidate they want to use, the candidate may go through a deliberate Production Graduation process toward a separately deployed production version.
Each active R&D month includes 2 Production Graduations.
Unused graduations do not bank.
The recurring economic distinction is:
$1,000/month Managed Operations = keep production operating.
$2,000+/month Chimba R&D = keep research operating.
The customer may use either service independently or both together.