# SCIENCIBLE — Public investor brief Reviewed: 30 September 2026 ## 01 · Origin and investment context SCIENCIBLE started in September 2024 from research work in the lab. Its purpose is to connect scientific understanding, practical exploration and the development of ideas, for people with and without a scientific background. This public brief describes the platform direction and distinguishes existing experiences from intended services. It is not an investment offer, a valuation, audited reporting or evidence of commercial traction. Incorporation details, ownership, funding terms and financial records are not published in this brief. The proposed customer groups include individual learners and makers, educators, research teams, companies, institutions and public-sector organizations. These are intended audiences, not a list of contracted customers. Official SCIENCIBLE school and campus chapters are distinct from independent organizations using the platform. ## 02 · Product and current delivery boundary The public website includes subject and channel navigation, source-linked NASA and MIT publisher updates, a research search experience using Europe PMC, and interactive inspection of existing 3D models. Europe PMC coverage is biomedical and life-science focused; it is not a comprehensive index of all science. Publisher updates are cached and are not real-time reporting by SCIENCIBLE. Guided model-observation activities connect learning pages to the Reality Workspace. Viewing or rotating a model does not establish simulation accuracy, engineering performance, editable product authoring or competency assessment. The signed-in experience includes demonstration workflows. Displayed activity, progress or project examples must not be used as investor traction or customer-usage evidence. A separate integration catalogue uses labelled contract fixtures rather than live training inventory. Organization administration, original editorial publishing, operational commerce, financial services, live collaboration and end-to-end assessed training require further delivery and acceptance testing. A published page or a described feature is not equivalent to a delivered service. ## 03 · Six complementary channels PYSTEP — What would you like to make? Accessible, executable creation for any person or profession, spanning visual and media authoring, interactive experiences, products and services. Layered vector and motion authoring is implemented; wider audio/video production, collaboration and publishing remain delivery work. Briefs and checklists are supporting tools, not the channel’s scope. LABS — How can I test and reproduce it? Protocols, variables, raw measurements, analysis and reproducibility records. LABS prepares the experiment; the separate Reality Workspace builds, replicates and validates supported spatial scenarios once runtime integration is available. A prepared package is not a completed simulation. FRONTIER — Intelligence, research, knowledge, analytical methods, techniques and innovation across disciplines. Source-excerpt AI synthesis, study-effect pooling and data analysis feed linked drafts in other arms. Broader discovery agents, licensed retrieval and specialist execution remain delivery work; spatial runtime and child-facing adaptation require separate acceptance gates. LIFE — All aspects of life and living: health, physical and mental wellbeing, nutrition, foods, home, family, care, accessibility and environment. Constraint-based food optimization and living-data analysis are implemented tools within that larger scope. Clinical services, sensitive health records, connected devices and product operations require dedicated qualified review, privacy and safety controls. FINANCE — What is it worth, and how is it funded? Financial education, funding, markets and financial media, with transactions and crypto services in the intended scope. Operational or regulated services require separate provider, legal and risk decisions. KIDS — How do young minds start? Age-appropriate science, creative art, games, video, learning and science/art kits. Adult oversight, safeguarding, consent and product suitability are release requirements, not assumptions. These channels organize one platform. They are not presented as separately incorporated businesses. Shared identity, permissions, content, search, projects and commerce should support the channels without duplicating services. ## 04 · Commercial model and validation Potential revenue routes are individual memberships, organizational learning and workspace access, digital learning products, physical products such as foods and kits, and scoped partnerships. These are business-model hypotheses; this brief does not claim realized revenue, active paid subscriptions, signed enterprise contracts or validated unit economics. Each route needs evidence before an investment case can be quantified: the paying customer, the specific paid benefit, purchase and renewal behavior, delivery costs, support burden, gross margin, acquisition channel and retention cohort. Proposed prices elsewhere on the platform are not proof that checkout or a paid service is operational. Market sizing should be built from named customer segments, sourced customer counts and a documented pricing assumption. No total-addressable-market figure is published here because a supported market study has not been supplied for this brief. A funding proposal must connect the requested amount and runway to costed milestones, accountable owners and measurable acceptance criteria. No raise size, valuation, instrument, committed investment or allocation percentage is asserted here. ## 05 · Technology delivery and integration gates The application and simulation platform are separate delivery responsibilities connected by a shared, versioned contract. Contract validation and consumer tests have been run locally in prior integration work; automatic enforcement in the managed release pipeline remains outstanding. The integration handoff describes staging identity, catalogue and session services as in progress. The next supported workflow is identity linking, real catalogue discovery, session creation, authorization, hosted runtime execution and authoritative session status. End-to-end staging execution has not been established by the public model viewer. Session launch must use the validated runtime origin returned by the session-creation response, strict origin and frame checks, short-lived authorization and explicit failure handling. User identity and access must be enforced by services, not inferred from a visible interface. Practice sessions do not issue competency credentials. Evidence-integrity testing and backend-controlled assessment status are separate gates. Passing a software test or displaying a completion badge is not a basis for a competency award. The wider delivery program also includes research and AI assistance, learning progress, editorial publishing, community and mentorship, innovation submissions, commerce, finance, institutions, companies, accessibility, child safety and operations. Simulation integration alone does not complete SCIENCIBLE. ## 06 · Milestones investors can evaluate Foundation: establish contract enforcement, identity and access boundaries, secure launch, operational ownership and a disposable staging test environment. Acceptance requires successful and rejected access paths, error recovery and traceable test evidence. Practical delivery: a permitted user discovers an actual scenario, runs it on a supported device and retrieves its authoritative status. Independently, a learner saves and resumes genuine progress. Neither flow should depend on fabricated activity. Channel delivery: enable creation and media production in PYSTEP; connect reproducible LABS experiments to the separate spatial runtime; combine research and innovation in FRONTIER; deliver practical wellbeing and supplier-backed food workflows in LIFE; build personal, business, market and digital-asset capabilities in FINANCE with regulated services gated; and deliver creative, interactive and supervised learning capabilities in KIDS. The six-channel build plan tracks current tools and remaining dependencies. Commercial validation: complete a real, approved purchase and fulfilment flow with payment verification, failed-payment recovery and accurate entitlements. Measure customer use and retention from consented records before publishing traction. Institutional scale: validate tenant isolation, role administration, cohort assignment, chapter governance and leader handover. Public-sector and high-stakes assessment commitments require their own deployment, accreditation and assurance work. No completion dates are promised in this brief. ## 07 · Material risks and diligence questions Execution risk: a broad platform can outpace its delivery capacity. Investors should inspect module ownership, dependency gates, acceptance evidence and costed sequencing rather than count website pages as product completion. Content and intellectual-property risk: scientific claims, learning material, media, models and products need provenance, rights records and review. Displaying third-party media does not prove SCIENCIBLE owns it, and no patent or exclusive-rights claim is made here. Privacy and security risk: personal data, institution records and assessment evidence require purpose limitation, role-based access, retention rules, incident response and tested recovery. This brief does not assert a completed independent security audit or certification. Safety and regulatory risk: child-facing services, health content, foods, payments and crypto introduce distinct obligations. Their availability must depend on appropriate review, permissions, qualified operational owners and approved providers. Commercial risk: willingness to pay, acquisition cost, retention and margins need actual cohort and transaction evidence. Model-viewing demonstrations and proposed subscriptions are not substitutes. Third-party dependency risk: source services, media rights, hosted runtime availability and payment infrastructure can change. Release decisions should include degraded-service behavior and documented alternatives. ## 08 · Investor review process Start with this brief and the public product routes, then identify the evidence you need using the document register. Each requested record should have an owner, version, period covered and an explicit access classification. Corporate records, beneficial ownership, capitalization, financial statements, cash balances, contracts and private security materials are not hosted on this public page. Their absence here means they are not publicly supplied; it is not a claim that the records do or do not exist. Use the inquiry form to introduce your organization, investment focus and requested materials. The form prepares a message for your review; it does not grant data-room access, execute an NDA or guarantee that a requested document is available. Do not send sensitive financial or identity documents through the general contact form. Any investment discussion must be supported by management-approved records and appropriate professional advice. This information page does not solicit or accept investments. ## Document register ### Public platform and investor brief Status: Public brief Origin, scope, channel strategy, delivery boundaries, proposed commercial model and risks. Download the current text below; this is not a pitch deck or audited financial report. ### Corporate identity and governance Status: Not published Request incorporation and jurisdiction records, legal entity name, beneficial ownership, governing documents, director appointments and material board approvals. ### Capitalization and funding history Status: Not published Request a dated, fully diluted cap table, share classes, options, convertible instruments, prior financing and any material shareholder rights. ### Financial statements and cash position Status: Not published Request the reporting period, management accounts, cash and liabilities, revenue reconciliation, accounting policies and any audit or review report that actually exists. ### Funding proposal and operating model Status: Not published Request the proposed instrument and terms, use of funds, costed hiring and delivery plan, runway calculation, assumptions and downside scenarios. ### Commercial traction and unit economics Status: Not published Request dated, consistently defined active-user and paying-customer metrics, revenue cohorts, retention, acquisition costs, margins and corroborating records. ### Market analysis and customer validation Status: Not published Request a sourced bottom-up market model, buyer interviews, competitive analysis, signed agreements where applicable and evidence of willingness to pay. ### Intellectual property and content rights Status: Not published Request founder and contractor assignments, software and model licenses, media permissions, trademark records and any substantiated patent filings. ### Architecture and delivery evidence Status: Not published Request versioned architecture, dependency and release registers, staging acceptance evidence, security test reports and a demonstration of supported end-to-end workflows. ### Privacy, safeguarding and operational readiness Status: Not published Request data maps and retention rules, access controls, child-safety procedures, incident response, business continuity, supplier checks and relevant regulatory advice.