Products & platforms
Explore the products and components we develop, their stages and the engineering capabilities behind them: identity, content, payments and operations.
Execution and risk, strategic decisions, AI evaluation and subscription content. Each product has its own scope and availability stage.
Execution & risk
Open source
An execution and risk management engine for crypto markets. It combines deterministic execution, risk controls and an event trail for auditing.
It is not an autotrader, does not predict prices and does not generate signals. Crypto trading involves risk of loss.
Strategic decisions
Early access
A situation room for context, evidence and decisions. AI-assisted analysis preserves strategic memory and human accountability.
AI quality
In development
A measurement and judgment layer for AI systems. It organizes evaluations and quality reports to support human review and the development of assistants.
Subscription content
Published editions
Operational reading of the BTC Futures market, with editions in an authenticated area. Plan-based access separates recent reading from available history and downloadable artifacts.
Operational preparation material. Not investment advice.
External reference · Food Process
A management platform for kitchens and restaurants, owned and operated by Food Process. Presented as an external reference for restaurant software.
Kulinaryos websiteThe portfolio also includes these development efforts and platform components.
In development
Transaction records and financial reports with an audit trail.
Architecture in the JournalProposed capability
Connecting AI costs and usage to business outcomes.
Architecture in the JournalAgent orchestration
Coordination of missions and agents, with states, sessions and execution controls.
About MaestroExperimental
A project for monitoring sustainable funding opportunities.
AI control
Control of AI calls through policies, routing and audit.
Architecture in the JournalAI evaluation
Reference datasets and criteria for AI evaluations.
Architecture in the JournalInterfaces and implementation
Explore the interfaces and engineering decisions in the code. Local captures and selected excerpts from main, with their source revision identified.
Selected product: Robson
The code checks the per-trade cap and the remaining budget before admitting an entry.
Enlarge capture in a new tab Robson interface from main, with synthetic data in a local environment.
Capture revision: ldamasio/robson · main · 0cef339 let cap = self.risk_per_trade_amount(capital_base);
if cap <= Decimal::ZERO {
return false;
}
let charge = if planned_risk <= Decimal::ZERO {
cap
} else {
planned_risk
};
if charge > cap {
return false;
}
self.remaining_budget(capital_base, budget_consumed, latent_risk) >= chargeImplementation capabilities
Publishing, identity and payments form the architecture of a paid content platform. Within the Engineering Partnership, the agreed roadmap defines the integrations and implementation responsibilities.
Content organized in a CMS, with files held in private storage.
Collection · Editions · FilesIdentity, plans and payments connected to each user’s permissions.
Account · Subscription · PermissionsA member area with reading and downloads authorized on the server.
Portal · History · DownloadsIdentity · Storage · APIs · Deployment · Observability
The architecture treats user data sovereignty as a requirement to define: hosting, permissions, export formats and recovery become part of the partnership roadmap and acceptance criteria.
Development paths for content platforms within RBX’s B2B strategy. Each can enter the Engineering Partnership roadmap according to the business model and user requirements.
Verifiable records of content origin and integrity, connected to identity and access rules. Private content and personal data remain off-chain, with their own storage and permissions.
Virtual spaces and 3D experiences for learning, events and communities, integrated with the platform’s identity and subscription system.
Contextual assistants, content discovery and text or voice interaction to personalize the experience, with consent, access control and quality evaluation.
Data sovereignty depends on the whole system: storage, key management, permissions and portability. Blockchain contributes verifiable records; the scope of each integration is defined and validated within the partnership.
The Portal and member area inform these technical capabilities. The references below describe the mechanisms; the content subscription and engineering partnership are separate engagements.
RBX Portal
Modules, risks, roadmaps and evidence in an authenticated area. Each person can access the projects for which they have permission.
Satwake / Briefing BTC
Editions, available history and artifacts in a member area. The public presentation describes plans and content access.
Public presentation and plansRBX Journal
The Journal itself uses the RBX content layer to publish articles and distribute them through RSS. The public technical report describes this flow.
Read the implementation reportAn ongoing product engineering partnership, with an agreed roadmap, responsibilities and acceptance criteria. Architecture, implementation and operations enter the scope according to the context.
R$8,000/month · 16 monthly hours of technical capacity