FUNA × KYZEL KREATES™ / 4P3X AI™

Our work
with FUNA.

Strategic partnership · active co-design & development

One partnership, many connected projects. Community software, solar infrastructure, engineering, learning and business systems, shaped through real requirements and repeated review.

Public overview updated . Workstream stages reflect the programme records reviewed through 10 October; later milestones require their own evidence.

CONNECTED WORK / SHARED PURPOSE

Concept illustration connecting a solar streetlight, a local computing node and a factory through an information layer
InfrastructurePeopleIntelligence
Illustrated programme relationships. This is an explanatory concept, with no site dimensions or engineering-performance claim.

THE WHOLE PROGRAMME

Different projects.
One continuing collaboration.

FUNA brings infrastructure requirements and operational knowledge. Ciaran Kelly and 4P3X AI™ contribute software, engineering representations, analysis, research and project communication. Partner feedback changes the work as the real constraints become clearer.

The sections below cover 16 connected workstreams. Each keeps its own status: a working software prototype, a calculated model and a physical installation require different evidence.

01 / Infrastructure & community

Connect the place to the people.

Lighting, communications, local facilities and community workflows need to be designed together.

01 / Infrastructure with a human purpose

Smart lighting & Turn on the Light

The initial brief connected off-grid lighting with asset information, system health, maintenance and community support. Turn on the Light gives that technical programme a human focus: the intended value of dependable lighting and services in the places people use every day.

Recorded stage: Active architecture and requirements work.

Work, evidence & next steps for Smart lighting & Turn on the Light

Our contribution

  • Mapped integration and operational-intelligence requirements around FUNA's existing hardware direction.
  • Connected lighting assets, telemetry, fault reporting and maintenance workflows in the programme design.
  • Separated intended social benefits from outcomes that would need field measurement.

Next evidence needed

Confirm manufacturer interfaces, operating conditions and an agreed validation plan before relying on integrations in the field.

02 / Mission, people and environment first

Community operations & co-design

FUNA's practical knowledge changed how we approached community systems. The design starts with the people involved, local conditions, participating organisations and the outcome they need. A software template is useful only after those realities are understood.

Recorded stage: An adopted design method with partner feedback.

Work, evidence & next steps for Community operations & co-design

Our contribution

  • Reconciled practitioner knowledge about community structures, patrol practice, reporting and evidence access with formal rules.
  • Distinguished community participation from recognised authority and specific operating permissions.
  • Fed stakeholder corrections back into the workflows instead of treating the original interpretation as fixed.

Next evidence needed

Keep testing complete journeys against actual community needs, responsibilities, accessibility and local conditions.

03 / Useful information when connections are imperfect

Networks, telemetry & maintenance

We reviewed the supplied telemetry architecture and retained suitable foundations. The resulting direction separates low-bandwidth operational messages from heavier media traffic, with local buffering and recovery considered from the beginning rather than added after a connection fails.

Recorded stage: Architecture and integration planning; field performance unverified.

Work, evidence & next steps for Networks, telemetry & maintenance

Our contribution

  • Examined sensing, secure ingestion, asset events, time-series information and reporting paths.
  • Kept low-power radio telemetry separate from high-bandwidth video transport.
  • Connected health monitoring, service scheduling, store-and-forward behaviour and recovery evidence.

Next evidence needed

Test real interfaces, radio conditions, message integrity and reconciliation after interruption using representative equipment.

04 / Planning the supporting environment

Base station, servers & off-grid facilities

The work expanded into the physical and digital facilities that a connected programme would need. These concepts bring communications, local computing, resilient power and service access into the same discussion so one discipline does not quietly undermine another.

Recorded stage: Conceptual facility and infrastructure design.

Work, evidence & next steps for Base station, servers & off-grid facilities

Our contribution

  • Explored base-station and server functions alongside solar and battery resilience.
  • Considered cooling, ventilation, physical security, fire protection and maintenance access.
  • Used visual representations to expose layout and operating questions for review.

Next evidence needed

Replace planning assumptions with site information, verified dimensions, engineering calculations and professional review.

02 / Engineering & visualisation

Make the design inspectable.

Stakeholder corrections shape the facility, energy architecture, digital twins and engineering questions.

05 / A visible stakeholder feedback loop

Smart-factory planning & revisions

Starting with a stakeholder layout, we developed an enhanced factory-planning interpretation and revised it following FUNA's corrections. The work considered how goods, people, quality checks, waste and service functions would move through the proposed facility.

Recorded stage: Iterative planning concepts; scale and layout questions remain.

Work, evidence & next steps for Smart-factory planning & revisions

Our contribution

  • Added receiving, quality-control, quarantine, stores, work-in-progress and rework considerations.
  • Explored training, staff facilities, utilities, spares and monitoring functions.
  • Revised the footprint, toilet arrangement and adjacent receiving and dispatch bays in response to the brief.

Next evidence needed

Resolve the remaining receiving-area ambiguity and verify the plan before detailed engineering or construction.

06 / Bringing hardware requirements together

4IR Micro-Grid Node

FUNA's specification, sketch and concept visuals became the basis for an evolving node design connecting energy, lighting, sensing, communications and local computing. Weight and cost objections materially changed the direction, demonstrating why stakeholder constraints must survive into the engineering model.

Recorded stage: Active co-design and digital engineering; no fabrication claim.

Work, evidence & next steps for 4IR Micro-Grid Node

Our contribution

  • Translated the supplied brief into inspectable system relationships and design questions.
  • Reworked an earlier, heavier concept towards the requested low-power direction.
  • Distinguished continuous essential functions from intermittent workloads and future options.

Next evidence needed

Confirm candidate hardware, mounting evidence, environmental limits and a bounded physical prototype programme.

07 / From visual inspection towards engineering evidence

Hardware twins & CAD progression

Successive browser twins preserve the design's evolution rather than overwriting earlier assumptions. Selectable parts and inspection views help people examine the concept. The CAD work adds a separate discipline: geometry must express supported design intent rather than turning a convincing picture into an engineering fact.

Recorded stage: Inspectable digital artefacts; physical correlation and sign-off remain open.

Work, evidence & next steps for Hardware twins & CAD progression

Our contribution

  • Produced versioned twins with orbit, touch, cutaway, exploded and flow views.
  • Developed a deterministic parametric-CAD path with geometry checks and engineering exports.
  • Retained unresolved structural inputs and withheld full project validation.

Next evidence needed

Bind geometry to verified materials, dimensions, mounting conditions and independently reviewed structural evidence.

08 / Make the assumptions visible

Power architecture & energy modelling

We modelled how generation, storage, lighting and computing demand could fit together. The design evolved towards protected energy domains and selective high-power operation, with autonomy treated as a calculation to test rather than a promise to publish as measured performance.

Recorded stage: Calculated concept models; whole-node power and autonomy unmeasured.

Work, evidence & next steps for Power architecture & energy modelling

Our contribution

  • Compared daily demand, available solar energy, usable storage and reserve assumptions.
  • Examined duty cycles, conversion losses, power sharing and on-demand workloads.
  • Kept safety protections and deterministic electrical control outside learned-model authority.

Next evidence needed

Measure representative rails and workloads, then test solar variability, battery condition, thermal pressure and recovery.

09 / Different surfaces for different jobs

3D worlds, interiors & command interfaces

The programme includes 3D worlds, interiors, Subterra, visualisations and cinematic work. A later architecture refinement separates an accessible browser command surface from deeper Godot simulation and training, while preserving useful existing environments and assets.

Recorded stage: Existing visual work plus an adopted dual-surface architecture direction.

Work, evidence & next steps for 3D worlds, interiors & command interfaces

Our contribution

  • Used spatial and cinematic representations to communicate systems and proposed environments.
  • Retained Godot work for movement, interactive equipment and scenario rehearsal.
  • Defined a browser-first command-interface direction sharing canonical asset and event identities.

Next evidence needed

Prove device performance, data binding, revision parity and the separation of simulated state from real operations.

03 / Software & services

Give each purpose a useful workflow.

Separate workstreams cover the company, learning, modelling and the Virtual Grid direction.

10 / From incident to accountable review

IMPI / Impimpi community software

We built and expanded an interactive community-safety demonstrator showing how information could move between people, devices, APEX and authorised human reviewers. Different stakeholder perspectives make the proposed workflow understandable before it becomes an operational system.

Recorded stage: Working simulated demonstrator; operational acceptance remains open.

Work, evidence & next steps for IMPI / Impimpi community software

Our contribution

  • Created simulated incident flows, triage, evidence review and audit surfaces.
  • Explored virtual patrols, Street Committees, device coverage and tracking concepts for assets, loved ones and animals.
  • Included network-loss and recovery scenarios, IMPI branding and an Afrikaans language option.

Next evidence needed

Validate workflows, privacy, permissions and recovery with the intended users before any live-service reliance.

11 / A separate organisational software workstream

FUNA company operating App

The company operating App addresses FUNA's organisational needs within the same partnership. It is tracked separately from community safety, education and carbon-data work so a requirement or acceptance decision from one product cannot silently become a claim about another.

Recorded stage: Active software workstream; no blanket production-acceptance claim.

Work, evidence & next steps for FUNA company operating App

Our contribution

  • Established the operating App as its own software development stream.
  • Applied the same requirements, release, acceptance and evidence discipline used across the programme.
  • Kept organisational software distinct from the public-facing and infrastructure systems.

Next evidence needed

Agree and verify complete operational workflows against the needs of their intended users.

12 / Education designed for access

FUNDA Online School

FUNDA is the programme's distinct education workstream. Its development direction prioritises local-first use, offline capability, language access and accessibility, recognising that a learner's connection and device should shape the design from the outset.

Recorded stage: Internal working prototype; customer and production validation remain open.

Work, evidence & next steps for FUNDA Online School

Our contribution

  • Developed an internal working prototype and education software direction.
  • Brought multilingual, offline and accessible-use requirements into the brief.
  • Kept curriculum acceptance and learner-facing validation separate from a successful internal build.

Next evidence needed

Complete curriculum, installation, offline, device and accessibility checks with appropriate reviewers and users.

13 / Explain the options and their assumptions

Website & lighting-retrofit calculator

The website and calculator work supports clearer communication with infrastructure stakeholders and property developers. The requested calculator compares lighting approaches across a long-term ownership period, making the difference between an illustrative model and a dependable decision input especially important.

Recorded stage: Modelling and communications workstream.

Work, evidence & next steps for Website & lighting-retrofit calculator

Our contribution

  • Framed the comparison around total cost of ownership rather than purchase price alone.
  • Identified tariffs, maintenance, financing, capital and emissions assumptions that affect results.
  • Connected public explanation with the need to keep modelling inputs explicit and current.

Next evidence needed

Validate inputs and calculation behaviour before external decisions rely on the outputs.

14 / From telemetry towards verifiable reporting

Virtual Grid™ & carbon-data systems

Virtual Grid explores how instrumented infrastructure could support digital measurement, reporting and verification. The work connects data collection with validation and reporting while keeping carbon rights, independent verification and commercial mechanisms as explicit unresolved questions.

Recorded stage: Active development direction; no live-grid or issued-credit claim.

Work, evidence & next steps for Virtual Grid™ & carbon-data systems

Our contribution

  • Mapped the proposed journey from node telemetry through transport, validation and reporting.
  • Examined verification, aggregation and issuance dependencies.
  • Kept existing partner IP, 4P3X IP and genuinely joint work distinct in ownership discussions.

Next evidence needed

Establish measurement quality, rights, methodology and independent verification before making environmental or credit claims.

04 / Research, governance & communication

Keep the work accountable.

Financial scrutiny, research, authority and clear communication support the wider programme.

15 / Challenge the model as well as the presentation

Investor communication & model review

We supported FUNA's investor-readiness work through presentation planning, narration and financial-model review. The work helps explain the proposed businesses and makes assumptions and supporting evidence easier for authorised reviewers to examine.

Recorded stage: Communication artefacts and model-review outputs produced; partner review is separate from funding outcomes.

Work, evidence & next steps for Investor communication & model review

Our contribution

  • Produced slide-specific narration, a timing map and a QA record.
  • Reviewed model structure, assumptions and consistency as part of private partner quality assurance.
  • Recorded review and follow-up items for FUNA.

Next evidence needed

Complete appropriate partner and specialist review before publishing or relying on investment materials.

16 / Turn useful evidence into better tests

Research, resilient compute & Guardian governance

An engineering evidence watch feeds research on edge AI, microgrids, video and resilient infrastructure back into the programme. It informed proposed compute-placement and resilience governors, while 4P3X Guardian AI™ supplies the authority framework: identity, permissions, review, audit, revocation and containment.

Recorded stage: Adopted architecture and qualification requirements; FUNA field implementation unverified.

Work, evidence & next steps for Research, resilient compute & Guardian governance

Our contribution

  • Made energy, heat, memory, connectivity, privacy and mission deadlines explicit scheduling constraints.
  • Developed replay, outage, interrupted-update and compound-failure test requirements.
  • Preserved human authority and treated AI detections as uncertain evidence inputs.

Next evidence needed

Test the proposed behaviour on instrumented hardware; external research results remain external evidence until reproduced.

THE DEVELOPMENT JOURNEY

The corrections are part of the work.

Requirements develop through discussion, inspection and revision. Earlier versions explain why the design changed.

  1. Discovery

    Start with the integrated brief

    Lighting, telemetry, community software and maintenance were considered together. Requests for interface documentation and sample data preceded integration promises.

  2. Partnership

    Build one relationship across distinct workstreams

    The engagement developed into an executed strategic partnership. Each software, engineering and business stream retained its own scope and acceptance questions.

  3. Co-design

    Build, listen and revise

    Interactive software, factory layouts and hardware twins made ideas inspectable. Stakeholder corrections changed workflows, physical constraints and the design direction.

  4. Engineering

    Expose the physical limits

    Energy models and CAD progression sharpened the distinction between a useful concept, a calculated result and evidence that still needs physical validation.

  5. Learning

    Feed the lessons back into APEX

    Operational feedback and external research strengthened mission-first design, governed authority, resilient-compute requirements and the next bench-test programme.

LEARNING FROM THE REAL CONTEXT

What FUNA taught the wider APEX programme.

The collaboration strengthens how 4P3X approaches other projects while preserving the separate evidence for each one.

The mission comes before the mechanism

Begin with people, environment and responsibilities. Check the finished workflow against the original need, including poor connectivity and limited power.

A correction is useful evidence

A practical constraint can outweigh an elegant earlier design. Keep the reason for the change so the same mistake does not return in another form.

Every claim keeps its own status

Partner feedback, a working prototype, a simulation, a calculation and a field measurement answer different questions. None should silently substitute for another.

Capability needs clear authority

Access, disclosure and consequential actions require defined permissions and accountable review. A confident AI output does not grant permission to act.

EVIDENCE & NEXT STAGES

Know what each result supports.

One strategic relationship contains multiple workstreams. Progress in one does not establish completion or acceptance of another.

How to read the FUNA programme record
Recorded workWhat it supportsNext proof point
Software & learningWorking demonstrations, internal prototypes and separately scoped development.Workstream acceptance, target-device, accessibility, offline and security testing as applicable.
Factory, hardware twins & CADConcept refinement, inspectable representations and bounded geometry checks.Authoritative dimensions, selected components, professional engineering review and physical validation.
Energy & resilienceCalculations from explicit assumptions and a defined qualification direction.Measured power, battery, thermal, communications and recovery behaviour on representative hardware.
Virtual Grid & carbonA measurement, reporting and verification development direction.Rights, methodology, independent verification and any issuance or operational evidence.
Partnership & business preparationA recorded strategic relationship, project development and investor-support outputs.Separate accepted work packages, appropriate specialist review and evidence for any commercial outcome.

This public account summarises the programme. Private correspondence, agreements, financial schedules, source files and protected engineering or build methods are excluded.

A PRACTICAL NEXT CONVERSATION

Discuss a defined workstream.

For a project review, partnership conversation or a similar development brief, start with the purpose, intended users and evidence needed.

START WITH SOMETHING SPECIFIC

What should we explore next?

Talk to Ciaran

Project film

Caption and text support is shown for each selected film.

Open the film room and written scene guide →

4P3X AI™ / LOCAL SITE GUIDE

Where shall we start?

Curated public guide. Not connected to the private AI runtime.

YOUR DEVICE / YOUR PREFERENCES

Make it easier to read.

Only this release’s display preferences are reset. Other Apps and stored data are not cleared.

Accessibility and media limitations →

Open this route →

Local settings boundary

The preserved /#admin route is a local demonstration boundary, not a live administration service. This release contains no server credentials, publishing controls or private project records.

Display settings are available separately. No publishing credentials are configured in this public release.