Your professional engagement workspace for consultation and project delivery.
The IYABOKO Project Client Portal is designed for clients with a consultation, Readiness Snapshot, Core Lab engagement, research project, simulation, prototype pathway, partnership programme, or enterprise agreement.
This page is for consultation and project clients.
For Silver, Gold, Platinum, or Institutional AI access and subscription resources, use the separate Member Workspace.
Open the records connected to your engagement.
Sign in with the account email associated with the consultation, payment, project intake, contract, or authorised organisation contact.
Reference, title, client, sector, Core Lab, and service pathway.
Stage, milestones, evidence requests, deliverables, reviews, and next actions.
Approved payment or invoice note, milestone approval, or scope change.
Use Project Support for missing records, access, billing, or engagement questions.
Your authorised engagement records
The live Core OS client-record module appears below.
A professional portal should answer the client’s essential questions.
Each approved record should make the current position, responsibilities, pending evidence, and next action clear.
Project Overview
Reference, client, service, sector, Core Lab, purpose, scope summary, and current stage.
Scope & Responsibilities
Deliverables, exclusions, client inputs, IYABOKO responsibilities, and change control.
Evidence Requests
Documents, datasets, decisions, approvals, stakeholder input, and specialist information required.
Milestones & Status
Current milestone, completed stages, pending reviews, dependencies, and target dates.
Documents & Deliverables
Approved reports, roadmaps, evidence packs, diagrams, simulations, or prototype documents.
Payments & Invoices
Safe payment status, invoice references, milestone billing, or scope-change information.
Meetings & Decisions
Approved meeting summary, decisions, action owner, evidence commitment, and follow-up.
Next Action & Support
Next action, owner, timing, support route, escalation, and external-review requirements.
A controlled pathway from consultation to closure.
Not every project uses every stage, but the same professional controls should guide delivery.
Intake
Define need, intended outcome, stakeholders, sector, and initial evidence.
Scope
Agree deliverables, exclusions, responsibilities, milestones, fees, and boundaries.
Evidence
Collect required documents, datasets, assumptions, permissions, and specialist input.
Delivery
Prepare the agreed report, roadmap, analysis, simulation, or prototype pathway.
Review
Complete quality checks, client review, change control, and specialist review.
Close or progress
Close the work or move into the next approved milestone or pilot.
One portal for the full IYABOKO delivery pathway.
The portal should display only sections relevant to the specific engagement.
Consultation & Readiness
Discovery, Readiness Snapshot, evidence-gap review, roadmap, boundaries, and next action.
Core Lab & Research
Sector evidence, research support, simulation priorities, datasets, and collaboration planning.
Simulation & Prototype
Requirements, architecture, test strategy, maturity gates, evidence, and pilot preparation.
Enterprise & Partnership
Multi-workstream scope, governance, milestones, coordination, reporting, and controlled pilots.
Every project record should identify the operating platform and Core Lab.
Cross-sector work may involve multiple platforms, but one lead pathway should be identified.
FlightCore Lab
Mission concepts, simulation, telemetry, architecture, evidence, and aerospace planning.
Open Space OS →Energy Continuity Lab
Solar, battery, microgrid, backup, resilience, and installer preparation.
Open Energy OS →Enature / Opuu Lab
Water, land, air, oxygen-flow context, biodiversity, soil, fire, and restoration.
Open Environment OS →BioContinuity Evidence Lab
Non-clinical research, evidence, data boundaries, ethics preparation, and readiness.
Open Health OS →Quantum Net Readiness Lab
Post-quantum preparation, secure routing, satellite-linked communication, and future networks.
Open Quantum Net OS →IYAMEGE Security Lab
Digital identity, blockchain governance, auditability, smart-contract readiness, and controls.
Open Financial Security OS →Expected a project record or deliverable but cannot see it?
Confirm that you are logged in with the authorised account and that the engagement has reached a stage where the record should be available.
Responsible Project Client Portal boundary.
The portal may display: approved scope, status, evidence requests, milestones, reports, deliverables, payment notes, meeting actions, support status, and next steps associated with the authorised client.
The portal should not expose: internal staff commentary, security logs, passwords, private keys, full payment-card data, confidential medical files, privileged legal records, unrelated client information, or unauthorised third-party data.
The portal is a professional engagement layer. It does not replace certified engineering systems, regulated clinical records, legal repositories, financial custody systems, emergency services, or regulatory authority platforms.
Review the engagement, complete the next action, and keep delivery moving.
Open authorised records, provide requested evidence, review approved deliverables, and use Project Support when clarification is required.