MAXIMUS INSTITUTIONAL ECOSYSTEM
MIPA and MAIOS are internal MAXIMUS governance layers for provenance, rights, versions, disclosure and human-controlled institutional workflows. They help organise evidence; they do not replace law, public registries, professional advice or authorised decisions.
MIPA is the internal intellectual-property documentation and controlled-disclosure framework used for the Organisation's own architecture, programmes, materials and recorded contributions.
It is designed to connect a knowledge object to its source, contributors, version, rights basis, permitted use, release decision and any external protection required.
MAIOS is the internal name used for an operating-system layer intended to connect registers, programme gates, decision owners, evidence and approved outputs.
The acronym is not expanded on this public page because an approved public expansion has not been provided. No certification, public authority, autonomous decision-making or adoption by any third party is claimed.
NON-SUBSTITUTION RULE
| Concept | What it establishes—and what it does not |
|---|---|
| Authorship evidence | Records who created or contributed material and when. It does not automatically prove ownership. |
| Ownership or licence | Depends on applicable law, employment or contractor terms, assignment, licence and chain of title. |
| MIPA record | An internal provenance, version and disclosure record. It is not a government filing or judicial finding. |
| Formal protection | A patent, trade mark, design or other filing made before the competent office where available and appropriate. |
| Permission to use | A defined licence, release or agreement covering the actual recipient, purpose, territory, term and derivative rights. |
MIPA WORKFLOW
The workflow is proportional to the object and the risk. External counsel and competent filings remain separate whenever the law or protection strategy requires them.
Register the knowledge object before broad circulation and preserve the attributable source.
Identify creators, contributors, pre-existing material and the evidence supporting each role.
Apply an internal handling level based on purpose, rights, confidentiality, privacy and security.
Document ownership, licences, assignments, approvals and unresolved third-party interests.
Authorise the exact version, recipient, purpose, channel, restrictions and required notice.
Obtain qualified advice and make competent-authority filings where legal protection requires them.
Record revisions, access, decisions, withdrawal, enforcement events and the current controlling version.
MINIMUM RECORD
An identifier without the underlying evidence, permissions and decision history is not a protection system.
Object title, type, purpose and programme relationship
Creator, contributor and source attribution supported by records
Creation, receipt, modification and review dates
Version, status, supersession and authorised source file
Known ownership, licence, assignment and third-party-rights position
Confidentiality, personal-data and disclosure classification
Permitted uses, recipients, expiry or withdrawal conditions
External filing, professional advice and evidence still required
MAIOS CONTROL MODEL
MAIOS may assist internal visibility and workflow consistency. The responsible human and legal entity remain identifiable for every decision and release.
Relate programme, framework, source, contributor, decision, risk, evidence and public statement without treating a presentation as proof.
Make required human approvals, missing evidence, professional review and entity responsibility visible before release or activation.
Identify the current approved derivative, preserve history and prevent an internal draft or superseded claim from becoming the public record.
Allow AI-assisted analysis or drafting only with named human ownership, source review, rights checks, limitations and release approval.
Search, structured records, comparison, workflow prompts, traceability, controlled drafts and evidence-linked reporting.
Ownership, legal validity, public approval, admissibility, professional conclusions, safeguarding action, partnership or publication.
CONTRIBUTOR & PARTNER RULE
A contributor to an approved MIBC NPIO workstream should receive the relevant authorship, contribution, confidentiality, data and permitted-use terms before providing protected material. General email and public enquiry routes are not secure evidence-deposit or IP-registration channels.
CONTROLLED WRITTEN ENQUIRY
The first message should identify the object, your role, the purpose of contact and the type of agreement or review required—without attaching confidential content.