KEDDEH TECHNOLOGY FAMILIES
Intelligence.
Where the work happens.
Explore the mechanisms, follow their working boundaries and understand how each specialised technology fits into the larger KEDDEH architecture.
BRAINK connects a requested action to its context, execution and retained result. The useful question is simple: can someone follow what happened, why it was permitted and what changed?
BRAINK familiesOne architecture. Distinct working roles.Understand the components by the work they perform, rather than treating every module as the same engine.
Distributed meshMany nodes. Work you can still follow.A mesh becomes useful when work can move between identified participants without losing its origin, result or recovery path.
WEB4 architecturesThe application is a doorway into the system.KEDDEH uses WEB4 as an architecture for connecting its preserved HTML environments with host services, named state and verifiable readbacks.
Edge nodesPut the working context where the work happens.An edge node is the local participant that holds the tools, information and permissions needed for a particular task.
Edge processingProcess locally. Transfer what the task needs.Local processing can reduce unnecessary transfer and keep an operator working through interruptions. Its benefit must be measured for the actual workload.
IL-LLM · Global ledgerLocal knowledge. Shared acceptance.The global-ledger role concerns how independently produced local records become accepted shared records, with their origins and disagreements intact.
IL-LLM · Immutable ledgerPreserve the record. Explain the correction.The immutable-ledger role preserves the history of assertions and state changes so that later readers can inspect how a result came to exist.
KEDDEH KoinService contribution with a traceable lineage.KEDDEH’s Koin concept ties recognition of service contribution to execution lineage: what a node performed and what evidence it retained.
BRAINK + CAN busFrom machine messages to accountable mesh workflows.KEDDEH identifies its BRAINK CAN bus and CAT6 multiprocess architecture as a specialised technology spanning equipment integration and vehicle retrofits. This journey separates the owner-described package scope from independently traced implementation evidence.
Mission technologiesKeep the mission working when the link does not.Local-first field readiness means the essential task remains usable with the resources actually available at the deployment site.
AerospaceIntelligence beside the mission team.A candidate application for local-first augmented intelligence is inspection and maintenance evidence that remains useful through constrained communication.
HealthcareSupport the professional. Preserve the basis.A candidate healthcare journey is accountable administration and evidence preparation, with authorised professionals retaining decisions about care.
Community servicesContinuity for the people doing the work.Local-first tools could help field teams retain case context and prepare clear handoffs when connectivity is unreliable.
Government & private sectorAccountable intelligence across organisational boundaries.A useful first deployment connects a defined intake, review and delivery process while preserving the organisation’s authority and record obligations.
Cybersecurity & cyber defenceDefence built around observable authority.The relevant BRAINK direction is accountable defensive operation: preserve evidence, constrain actions and verify what changed.