Shared project foundation
Private project records, revision-aware saves, exports and provenance links are reused by the new studios. Existing account flows and the member Lab remain separate.
One platform · distinct capabilities
Start with a purpose, not a qualification. PYSTEP supports executable creation across everyday, creative and professional work. FRONTIER supplies intelligence, research, knowledge and techniques across all arms. LIFE concerns health, food and all aspects of life and living. LABS handles experimental design, measurement and reproducibility. Reality Workspace is the shared spatial engine—not another name for LABS.
Private project records, revision-aware saves, exports and provenance links are reused by the new studios. Existing account flows and the member Lab remain separate.
LABS prepares the protocol and reference measurements. The supplied runtime handoff covers identity, catalogue and session services, still marked in progress. Arbitrary experiments require an agreed scenario/input mapping.
Each capability below has an owner, dependency and acceptance outcome. Planned services are not launch buttons. Layered vector/motion authoring, source-linked AI, quantitative analysis, food optimization, financial stress simulation and visual coding are implemented. Full audio/video production, advanced living services, financial transactions, supervised child accounts and operational commerce remain delivery work.
Open a tool. Make something.
PYSTEP is the requested replacement for the former WORLD arm, using Sciencible’s visual theme. The source application has not yet been supplied. Earlier saved artwork remains accessible separately; it is not the PYSTEP app.
Open PYSTEP studioActual PYSTEP replacement is blocked on the source project or reference. Renaming the workspace and retaining an older editor does not complete that integration.
See the full six-channel build planOwner: App
Depends on: Existing Sciencible sign-in; namespaced source port and membership controls
Acceptance: Create a space; invite a collaborator; retain chat and editable studio pipelines; deny outsiders and revoked members. Focused acceptance is recorded in the delivery tracker.
Owner: App + PYSTEP project owner
Depends on: PYSTEP source export and reference; compatibility and permission review
Acceptance: Port the actual PYSTEP workflows, preserve functionality, apply Sciencible colours and verify its acceptance cases.
Owner: App
Depends on: User-authored geometry; private versioned notebook
Acceptance: Add, move, resize, recolor, reorder and undo layers; scrub/play motion; export static/animated SVG; save and reopen exact editable state.
Owner: App
Depends on: Existing account and private project service
Acceptance: Create your own brief; calculate duration; save, reopen and export it.
Owner: App + media team
Depends on: Media processing, asset storage, rights and moderation
Acceptance: Edit source media, render output and recover failed jobs without losing the project.
Owner: App
Depends on: Versioned assets, permissions and publishing moderation
Acceptance: A permitted collaborator edits; a reviewer approves; a published version retains attribution.
Owner: App + Claude for spatial runtime
Depends on: Channel provenance and reviewed runtime contract
Acceptance: Carry the same project lineage into FRONTIER, LABS and a supported spatial scenario.
Owner: App + creator tools
Depends on: Sandboxed execution, asset lifecycle, deployment and rights review
Acceptance: Create an executable artifact, edit behavior, test it and publish an explicitly approved version.
Owner: App + domain specialists
Depends on: Domain-specific authoring, format interoperability and review
Acceptance: Produce an editable domain artifact with provenance, not only a written brief.
Open a tool. Make something.
Explore a visual experiment bench across physics, electrical and mechanical engineering, chemistry, biology, acoustics and colour. Change model parameters, inspect traces, compare a baseline and carry simulated data into analysis. Protocol, statistical comparison and uncertainty tools remain available.
Open LABS studioThe bench runs seven bounded analytical models with schematic apparatus. It is not a complete equipment catalogue, validated multi-physics environment or connected instrument system. Separate Reality runtime execution and institutional teaching controls remain outstanding.
See the full six-channel build planOwner: App
Depends on: Seven bounded equations; schematic apparatus, not connected hardware
Acceptance: Change parameters; inspect model assumptions and traces; pin a baseline; export exact inputs and outputs.
Owner: App
Depends on: Unit-consistent observations; reviewed independence/distribution assumptions
Acceptance: Compute Welch or paired t statistics, degrees of freedom, two-sided p-values and 95% intervals; propagate independent standard/rectangular components; export original inputs and method. Not calibration certification.
Owner: App
Depends on: User observations; bounded factor settings
Acceptance: Reproduce fitted values and residuals, generate all low/high combinations in a seeded order, export the run sheet and retain research provenance.
Owner: App
Depends on: User-entered measurements and existing private storage
Acceptance: Compute means and sample spread; retain units and steps; export and reopen the saved record.
Owner: App + laboratory partners
Depends on: Instrument adapters, calibration records, data provenance
Acceptance: Import real observations with units and calibration; reproduce the analysis from retained raw data.
Owner: Claude: runtime; App: experiment-to-scenario mapping
Depends on: Supported scenario mapping, geometry/material input contract, identity/session services and evidence callback
Acceptance: Launch an authorized scenario using the saved protocol; collect authoritative results; compare against the declared tolerance.
Owner: App
Depends on: Reviewer permissions and immutable protocol versions
Acceptance: Another authorized person repeats a pinned protocol and records an independently attributable result.
Open a tool. Make something.
FRONTIER and LIFE share one workspace for source-linked knowledge, technology, methods, scientific models and living systems. Build a private connected repository, synthesize supplied evidence, analyze data, explore scenarios and retain home, nutrition and environment work in the same project.
Open FRONTIER studioFRONTIER is the shared knowledge and intelligence arm, not just a reading list. It supplies evidence and methods across the platform. LABS owns experimental records; Reality Workspace owns supported spatial execution. Child-facing adaptations need separate review.
See the full six-channel build planOwner: App
Depends on: Private versioned notebook; source links and user-authored records
Acceptance: Create and link research/design/method records; prepare selected evidence for explicit synthesis; reopen old LIFE projects.
Owner: App
Depends on: User-entered cash-based assumptions in one currency
Acceptance: Recalculate three revenue cases and discounted cash flow; export reproducible monthly results; reject out-of-range growth.
Owner: App
Depends on: Seven bounded equations; schematic apparatus, not connected hardware
Acceptance: Change parameters; inspect model assumptions and traces; pin a baseline; export exact inputs and outputs.
Owner: App
Depends on: Signed-in account; supplied excerpts; configured AI service; explicit send consent
Acceptance: Generate schema-checked claims and techniques referring only to supplied source IDs; retain quotations; create linked destination drafts and proposed LABS protocol fields.
Owner: App
Depends on: Compatible study effects and standard errors; user datasets
Acceptance: Reproduce pooled effects, intervals, weights, Q and I²; export the method and data; reject incompatible structural inputs.
Owner: App
Depends on: User-provided source URLs and existing project storage
Acceptance: Reject malformed/duplicate sources; keep opposing evidence and limitations; save and export the brief.
Owner: App
Depends on: Existing Europe PMC search and NASA/MIT feeds
Acceptance: Use the retained source tools; keep their scope and dates visible; handle provider unavailability.
Owner: App + research editors
Depends on: Broader licensed indexes, extraction, citations and review
Acceptance: Produce reproducible searches and source-linked synthesis without invented findings.
Owner: App + innovation team
Depends on: Submission/review services, IP handling and FINANCE linkage
Acceptance: Submit an actual challenge entry, review it and track the approved development milestone.
Owner: App + research owners
Depends on: Licensed corpora, retrieval evaluation, sandboxed computation and specialist validation
Acceptance: Retrieve attributable evidence across disciplines, evaluate competing methods, run approved analysis and propagate versioned results across arms.
Owner: App + domain and child-content reviewers
Depends on: Provenance, audience policies, review approval and receiving-tool contracts
Acceptance: Preserve evidence lineage into every permitted consumer; child-facing material passes review rather than inheriting unrestricted AI output.
Open a tool. Make something.
LIFE tools now live inside the combined FRONTIER + LIFE workspace. Existing LIFE projects remain accessible without deleting or rewriting their saved records. Home resources, food optimization and living-data tools sit alongside research, knowledge records and models.
Open LIFE studioLIFE applies intelligence to living systems and everyday needs. Research techniques arrive from FRONTIER; experiments belong to LABS. Clinical care, medical records, connected devices and health interventions require qualified oversight and dedicated privacy controls.
See the full six-channel build planOwner: App
Depends on: User-entered quantities, rates and routine times; existing private notebook
Acceptance: Calculate energy/water and costs, compare a baseline, compute overnight rest, detect role conflicts and export or save exact inputs. This is personal planning, not a connected service.
Owner: App
Depends on: User-supplied food-label data and chosen constraints
Acceptance: Compute the lowest-cost feasible 0–4-portion combination, retain label references, exclude unknown/unchecked labels, export quantities and report infeasibility honestly.
Owner: App
Depends on: User-entered paired measurements with consistent units
Acceptance: Analyze actual supplied measurements; retain raw rows; export fitted values; never turn a statistical association into diagnosis.
Owner: App
Depends on: User-entered recipe quantities and private storage
Acceptance: Scale every ingredient, track selected days and reopen the saved plan.
Owner: App + qualified nutrition reviewers
Depends on: Licensed nutrition data, complete allergen provenance and review
Acceptance: Trace nutrient calculations to actual foods; never infer an allergen is absent from missing data.
Owner: App + food operations
Depends on: Approved suppliers, product evidence, payments, stock and fulfilment
Acceptance: Complete an approved purchase and delivery with accurate inventory and safety information.
Owner: App + qualified health partners
Depends on: Consent, sensitive-data controls and validated device integrations
Acceptance: A user can consent, revoke access and export their own data; no unsupported diagnostic claims.
Owner: App + qualified health and safeguarding owners
Depends on: Consent, sensitive-data governance, validated interventions and referral workflows
Acceptance: Deliver reviewed interventions or care workflows with authorized access, appropriate escalation, outcome measures and user-controlled retention.
Owner: App + living-systems specialists
Depends on: Constraint models, local/service data, accessibility and household permissions
Acceptance: Execute household/resource planning against actual constraints and data; measure outcomes rather than display generic advice.
Open a tool. Make something.
A dedicated modelling workspace for business cash-flow scenarios, economic market models, financial stress paths and manual account reconciliation. Compare cases, inspect assumptions and export calculations. Payments, banking, live market data, trading and crypto execution still require approved provider integrations.
Open FINANCE studioFINANCE spans personal and business finance, markets, funding and digital assets. Planning tools do not execute transactions, hold assets, provide personalized advice or replace regulated providers.
See the full six-channel build planOwner: App
Depends on: Illustrative linear curves and interior equilibrium
Acceptance: Calculate consumer/producer prices, tax revenue and deadweight loss; reject invalid interior solutions.
Owner: App
Depends on: User-entered cash-based assumptions in one currency
Acceptance: Recalculate three revenue cases and discounted cash flow; export reproducible monthly results; reject out-of-range growth.
Owner: App
Depends on: User-entered single-account statement, opening cleared balance and transactions
Acceptance: Calculate exact minor-unit balances, flag duplicate references, separate transfers/refunds and carried items, compare budgets, export inputs/results and retain editable notebook data. No bank connection or transaction execution.
Owner: App
Depends on: User-selected return, volatility, inflation and cash-flow assumptions
Acceptance: Run 500 reproducible paths, export terminal outcomes and methodology, preserve assumptions, and distinguish simulation fractions from market probabilities.
Owner: App
Depends on: User-entered values in one reporting currency
Acceptance: Recalculate allocations, P/L and amortized payment; save assumptions and export results.
Owner: App + approved finance providers
Depends on: Provider choice, user consent, jurisdiction and accounting requirements
Acceptance: Reconcile imported transactions and balances; revoke access; generate traceable exports.
Owner: App + licensed data providers
Depends on: Market licenses, corporate actions, valuation timestamps and risk methodology
Acceptance: Track authoritative prices and positions; label simulated orders separately from real execution.
Owner: Licensed providers + App
Depends on: Provider selection, region eligibility, identity checks, legal and operational review
Acceptance: Execute only explicit user-authorized transactions; handle rejection, reconciliation and audit records.
Owner: Approved digital-asset providers + App
Depends on: Network/provider selection, custody model, sanctions/AML controls, signing and risk review
Acceptance: Never collect seed phrases; verify network/asset/fees, request explicit signing, track finality and failures.
Owner: App + finance editors
Depends on: Deal permissions, disclosures, moderated publishing and funding partners
Acceptance: Review a real funding application with traceable documents; distinguish education from offers.
Open a tool. Make something.
Use the invention lab, program a virtual robot with loops and obstacle sensing, design visual compositions, read connected conceptual guides and explore the original box catalogue. Local tools retain session-only work without public sharing, child accounts or personal details.
Open KIDS studioKIDS owns age-appropriate interaction, creative making and guided discovery. This session-only playground does not create child accounts or share work publicly. Supervised accounts and physical kits require separate safeguards.
See the full six-channel build planOwner: App
Depends on: Local restricted teaching language; no arbitrary code execution
Acceptance: Run loops and obstacle conditionals, step the trace, reject collisions and runaway programs, and export the session.
Owner: App
Depends on: Seven bounded equations; schematic apparatus, not connected hardware
Acceptance: Change parameters; inspect model assumptions and traces; pin a baseline; export exact inputs and outputs.
Owner: App
Depends on: Original SCIENCIBLE KIDS BOXES.pdf; bounded app-authored models
Acceptance: Filter 550 exact titles in 55 categories and five original age bands; test ramps, resistors, gears and torque; solve logic puzzles; record and export experiments. Not 550 simulators or physical-kit instructions.
Owner: App
Depends on: Bounded local drawing interpreter; session-only state
Acceptance: Run user-built block sequences, animate and step drawn lines, reject out-of-bounds paths and export original artwork without accounts or uploads.
Owner: App
Depends on: Idealized energy equation and session-only state
Acceptance: Change height, predict speed, record outcomes and draw/export original art; no personal data or external chat.
Owner: App + child-learning specialists
Depends on: Reviewed age bands, learning design, accessibility and safe content
Acceptance: Complete age-appropriate activities with understandable feedback and accessible controls.
Owner: App + safeguarding owners
Depends on: Consent/age policy, verified adult permissions, retention and moderation
Acceptance: An authorized adult manages access; unauthorized sharing and contact are blocked; data can be removed.
Owner: App + kit operations + Claude runtime
Depends on: Product safety/age suitability, fulfilment, approved child-safe scenarios
Acceptance: A supervised learner follows a reviewed activity; adult purchase and runtime authorization remain separate.
Integration responsibilities: the app team owns channel workflows, project lineage and the consumer interface; the runtime team owns supported spatial scenarios, execution and authoritative evidence. Management and qualified partners own regulatory, safeguarding, content-rights and product-safety approvals. These are proposed delivery responsibilities, not a claim of staffing or agreed delivery dates.
Platform and investor context