A Modular Business and Provision Model for Amanah Companions

Amanah Companions does not need to manufacture every device that may one day support a person.

It does not need to build every artificial intelligence model.

It does not need to employ every therapist, engineer, communication specialist, technician, or caregiver.

And it should not attempt to become the institution that owns every part of a disabled person’s life.

The more important question is:

Can a person-governed continuity system coordinate useful assistive technologies, qualified services, and long-term support without requiring one company to own every component?

This is a business question.

It is also a question about access, sustainability, accountability, and what happens when a supplier leaves.

Amanah’s proposed answer is a modular provision model.

The product is not the whole service

A person may obtain an assistive device and still be unable to use it effectively.

The device may require configuration.

Someone may need to adapt communication vocabulary, explain controls, provide training, arrange repair, or replace equipment when it fails.

A family may purchase software but receive no practical assistance when the service changes.

A centre may install a technology without understanding how its use affects the person’s autonomy, communication, or privacy.

The World Health Organization’s assistive-technology framework treats people, policy and finance, products, service provision, and personnel as interdependent.

Amanah’s proposed commercial architecture begins from that distinction.

Selling a product is not the same as establishing durable support.

The provision process matters as much as the object being provided.

Mithaq Praxis as architect and orchestrator

Under the proposed model, Mithaq Praxis would develop the digital continuity architecture and coordinate a network of suitable service and technology providers.

Its responsibilities could include:

• developing the continuity spine and its governed data structures;
• maintaining software interfaces and portability specifications;
• defining capability and risk requirements;
• designing permission, review, and source-trace mechanisms;
• integrating compatible assistive tools;
• coordinating approved provision and service workflows;
• and establishing responsibilities for maintenance, support, replacement, and exit.

External partners might provide specialised software, communication equipment, accessibility assessment, configuration, installation, training, repair, or other services.

These responsibilities would need to be contractually defined.

Mithaq Praxis would not acquire clinical authority merely because it coordinates a service.

A supplier would not gain unrestricted access to personal records merely because it manufactures a device.

A purchaser would not acquire universal decision authority merely because they pay.

The company may own its implementation. The person’s continuity must remain governed for the person’s benefit.

Begin with what can be supported safely

The first offering need not contain a robot.

It might begin with a person-owned continuity toolkit.

A communication passport.

A preferences and accommodations profile.

A routine or transition plan.

A handoff summary prepared from reviewed information.

A portable record of what helps, what does not help, what remains uncertain, and who may receive particular information.

These are comparatively bounded possibilities. They would still require accessibility, privacy, security, accuracy, and appropriate user testing.

But they need not begin with clinical interpretation, continuous monitoring, autonomous decisions, or physical intervention.

The first commercial hypothesis is therefore deliberately modest:

Can Amanah provide useful, accessible, portable continuity tools before introducing more complex AI or devices?

If a manual document meets the need, it should remain available.

If deterministic software performs the task reliably, generative AI need not be involved.

If no device is necessary, provision should not create a reason to sell one.

A network of capabilities, not an unrestricted marketplace

A modular business model may eventually involve many suppliers.

That does not mean every available product belongs inside Amanah.

The system would require a defined pathway for assessing compatibility, intended use, evidence, accessibility, privacy, maintenance, liability, and risk.

The governing principles developed in Amanah’s first two research series must remain active.

Permission follows the capability and its context.

Machine-generated hypotheses do not become approved care instructions automatically.

The supported person remains the continuity subject.

Communication and refusal remain meaningful.

Operational care records are not default training material.

The system must not become a surveillance or obedience platform.

And a device must not inherit the whole continuity archive simply because it has been connected.

A future supplier should receive only the information and technical authority necessary to fulfil the approved task.

Amanah would coordinate qualified provision, not operate a marketplace in which purchasing a component automatically unlocks a new form of control.

Revenue without captivity

A sustainable service requires revenue.

Software development, accessibility testing, security, support, localisation, maintenance, training, and replacement all carry costs.

Possible income could eventually come from digital products, optional hosted services, institutional licensing, configuration, integration, training coordination, or contracted provision.

These are candidate revenue streams, not validated demand.

The critical distinction is between charging for a service and making a person dependent on continued payment to retain their history.

Amanah should not make personal continuity a hostage of subscription status.

Canonical records should be portable. Exports should preserve useful structure, source status, and permissions. The person should have a practical means of leaving a provider without beginning again.

This does not mean every service must be permanently free.

It means that the financial model must separate the cost of continuing an optional service from the person’s ability to recover and use their legitimate records.

Mixed revenue and equitable access

Amanah should not assume every individual or family can pay.

Possible models include directly purchased low-cost tools, institution-funded access, public procurement, subsidised provision, charitable support, cooperative arrangements, and future endowments.

Different mechanisms may work in different countries.

Their feasibility requires research.

Cross-subsidy may support access, but it cannot be promised without reliable funding.

Similarly, charity should not become a justification for public services to abandon their responsibilities.

The business model should identify who pays, who receives the benefit, who controls the information, who carries responsibility, and what happens when funding ends.

These may be different parties.

The body remains a later question

Amanah may eventually coordinate physical assistive devices.

The appropriate partner could be a manufacturer, robotics laboratory, specialist supplier, rehabilitation service, or qualified installation and maintenance provider.

But a device would enter Amanah only through a bounded capability and a separate safety case.

The initial embodied task might be as limited as bringing a communication device across a controlled room.

It would not establish permission for physical care, medication, mobility assistance, autonomous emergency intervention, or general household control.

Hardware procurement cannot bypass the governing spine.

Nor can a supplier’s technical certification replace person-specific acceptability, consent, operational safety, or accountable human supervision.

The business network must remain answerable to the purpose of care.

What happens when a provider leaves?

A lifelong continuity system cannot assume that companies last forever.

Suppliers may close.

Models may be retired.

Devices may be discontinued.

Service contracts may end.

Families may relocate.

Funding arrangements may change.

The proposed provision network must therefore treat replacement, export, repair, and succession as part of its design.

Mithaq Praxis should be able to change a technology provider without forcing the supported person to reconstruct their life.

A device should be replaceable.

A model should be replaceable.

A contractor should be replaceable.

The person’s continuity should not be treated as replaceable.

The research proposition

The proposed Amanah business architecture is not a claim that Mithaq Praxis already operates an assistive-technology supply network.

It does not establish regulatory approval, commercial viability, clinical effectiveness, or demand.

Those claims would require separate evidence.

The proposition is narrower:

Can a creator-led technology practice develop a person-governed continuity platform and coordinate qualified external provision, while keeping each capability bounded, each supplier accountable, personal records portable, and useful support financially accessible?

That question can be tested incrementally.

Begin with low-risk digital tools.

Evaluate real usefulness and accessibility.

Demonstrate privacy and portability.

Establish a responsible provision process.

Introduce partners only where their contribution is necessary.

And expand toward hardware only when the evidence justifies it.

The companion does not have to be the factory.

The factory does not have to own the companion.

And neither should own the person.

The continuity belongs with the life it serves.

Research status

This essay extends Amanah Companions Series I and II, particularly the work on the continuity spine, Stem Cells, risk-tiered permissions, care memory, model portability, succession, and embodiment.

The proposed commercial structure remains an authorial research proposition. No supplier network, pricing model, clinical service, hardware deployment, or commercial demand is established by this essay.

The WHO-GATE assistive-technology framework provides a relevant foundation for person-centred products, provision, personnel, and policy. It does not validate this specific Amanah business model.

Amanah would require further accessibility research, disabled-person participation, legal and regulatory review, business validation, qualified service partnerships, and evidence from bounded prototypes before real-world deployment.

Selected references

• World Health Organization, Global Cooperation on Assistive Technology (GATE).
• World Health Organization, Improving Access to Assistive Technology.
• UNICEF, When AI Becomes a Friend: Child Rights Risks, Harms, and Regulatory Responses to AI Chatbots and Companions, June 2026.