HAIA – The Human Artificial Intelligence Assistant Ecosystem

How HAIA Came to Be

The practice and the frameworks that became the HAIA ecosystem date back to Factics in 2012. The name itself was an attempt to make communication more casual with AI after injury limited use of my right arm. A name for the thing I was speaking with: HAIA, Human Artificial Intelligence Assistant. It carried a few versions as I made my way through the frameworks: Human AI Intelligence Architecture, Human Augmented Intelligence Architecture, Human AI Augmentation, others. After settling into the ecosystem, I decided to keep it as it originated, Human Artificial Intelligence Assistant (HAIA).

There was no plan, only the practice of using LLM or AI to assist me, the human, to do things, be it marketing content, social media posts, work letters, kids’ school letters, correspondence with legal assistants and lawyers, everyday email response, even the Governing AI book.

As this was not an intentional practice to build anything, the reactive practitioner work of operationalizing tools to solve AI’s real problems became something I needed to backtrack on and structure. Each aspect was a response to an AI failure, a limitation, or a risk that surfaced in real use. I built prompts and frameworks to solve issues as I encountered them.

In summer 2025, I completed the Elements of AI course and the Ethics of AI course, offered and credited by the University of Helsinki. That led to the adoption of academic rigor in studying the thought leaders who shaped AI, from builders to ethicists to policy figures. I built a thought leader list to learn who had influenced AI and how. The study of their publications, paired with simulated AI reviews from their perspective, shaped the work that followed and became the basis for the book Minds That Bend the Machine.

This page stands alone, updated periodically to share the HAIA ecosystem and the frameworks that influence it, from AI Governance to Content and Social Tools.

The ecosystem at a glance. Factics, HAIA-RECCLIN, and HAIA-CAIPR stack in sequence, with Checkpoint-Based Governance running across all three rather than sitting on top of them, because adding it at any level is what converts a practice from Responsible AI into AI Governance. HEQ and AIS measure the person doing the governing. The dashed panel holds the policy and infrastructure layer, built or specified and not running, and that separation is the point.

A walk through the ecosystem and why each piece exists.

Start Here

Each framework in daily use now has its own page, written for a general reader, with the full paper linked from it.

Factics: the evidence discipline underneath everything, and the only one that needs no AI at all.

Checkpoint-Based Governance: where a named human holds binding authority, and why presence is not authority.

HAIA-RECCLIN: the ten fields that make any AI show its work, and the workflow that spreads jobs across platforms.

HAIA-CAIPR: running one task across several platforms at once and reading the disagreement.

HEQ and AIS: measuring the governance competence at the center of AI literacy.

AI Provider Plurality: the policy layer, including GOPEL, HAIA Agents, and VAISA.

How I Work

This page is the living reference for how I do my work: the method governance and standards behind my AI use, my policy work, and my research practices. My initial AI use was limited to ChatGPT, then Perplexity for sources. In 2025 I openly disclosed I was working in a five model Multi-AI use system that was in practice but was not named. The first published HAIA framework was The HAIA-RECCLIN Model draft in September 2025, and the method’s first full deployment in practice produced Governing AI: When Capability Exceeds Control. The original story and architecture live in the founding paper, HAIA: Human Artificial Intelligence Assistant, which stands as published. This page carries the current state. The purpose, in plain language, is in The Other AI: What “A Human-AI Collaboration” Should Look Like, the first-person account of why this ecosystem exists and how the method runs.

Everything runs under Checkpoint-Based Governance: a named human stays in control at defined checkpoints, nothing advances without human approval, and disagreement is preserved instead of smoothed away. Every work product carries a maturity status: a rough draft holds the first third of the governance work, a working paper has passed Cross AI Platform Review and independent Navigator review with human oversight and holds two thirds, and a final publication is fully CBG compliant with its SCOPE source documents complete. For every claim that carries weight, the primary source settles the question. The platform run surfaces what needs checking, the independent synthesizer narrows the field, and a human reading the original record certifies it.

In Use

Method Governance, the process for creating content

• Factics: The foundation since 2012. A fact, a tactic, and a KPI set before any AI touches the work, so every claim carries its evidence and its purpose.
• Checkpoint-Based Governance (CBG): Constitutional authority layer with binding human checkpoints. Version 5.0, March 2026.
• HAIA-RECCLIN (Researcher, Editor, Coder, Calculator, Liaison, Ideator, Navigator): Seven-role reasoning and dispatch framework that makes the AI show its work: role, task, output, sources, conflicts, confidence, expiry, Factics, recommendation, and decision. Third Edition published March 2026.
• HAIA-CAIPR (Cross AI Platform Review): The same task run in parallel isolation across independent platforms, minimum three, drawn from a working pool of fifteen models across thirteen platforms spanning American, French, Swiss, Singaporean, and Chinese lineages. The count is diagnostic and never a vote. Agreement with no dissent anywhere on a material claim is treated as a flag, and minority positions are preserved rather than aggregated away. The working AI stays out of the run on purpose and serves as the independent synthesizer and fact checker alongside the human, with its synthesis held to the highest scrutiny and traceable to the raw returns. Fourth Edition published September 2026.

Tools, the process for distributing content

• HAIA-WOPPA (WordPress Optimization Publication Prompt Architecture): WordPress publication packager producing paste-ready Support and Content documents from finalized work.
• HAIA-SMART (Social Media AI Rating Tool): Six-pillar social content rating with Visual Intelligence Module, Multi-Platform Output Suite, AI Pattern Risk Detection, and Dissent Log.
• HAIA-CORE (Content Optimization Reader Evaluation): Substance evaluation for blog and long-form content.
• HAIA-MOON (Multimedia Operational Outputs for NotebookLM): Production prompts for cinematic video, deep dive audio, and infographic outputs, with steering and disclosure controls.

Record Keeping, how I prove the methods and the work

• HAIA-CARCS (Compliance Accountability Record and Case Study): Ten-section accountability record of what happened, who decided, and on what evidence. Its decision taxonomy separates a human who caught an error from a human who approved without reading, which a log of approvals cannot do.
• HAIA-SCOPE (Source Custody Observable Publication Evidence): Per-citation source custody record documenting the human source audit that moves a working paper to a finished publication.

Evaluation, how I know I am cognitively developing and collaborating

• HEQ (Human Enhancement Quotient) and AIS (Augmented Intelligence Score): Measurement framework for the governance competence at the center of AI literacy: the ability to direct, challenge, verify, and own the work done with AI. Four dimensions average into the AIS, with the HAIA-HEQ operational prompt for measurement runs. It scores the method rather than the answer. Growth is measured, and so are diminished returns and decline. First published September 2025, formalized December 2025, current working paper September 2026.

Platforms and Models, the pool the work is drawn from

Fifteen models across thirteen platforms, as recorded in the HAIA-CAIPR Fourth Edition roster, September 2026. This is a rotation and not a dispatch. Any session draws a subset, and the count in a session is the number of returns from the platforms dispatched. Search capability, retrieval backend, persistent memory, and reasoning visibility change with vendor releases, so the roster carries a date of record rather than a date of publication, because a roster ages the way a finding does.

Thirteen platforms, fifteen models. Eleven platforms expose one model each and two expose two, which is why the model count exceeds the platform count. Access route and lineage are the two fields most likely to cluster returns that look independent, and both are visible here before any dispatch is written. In RECCLIN Dispatch, each role goes to the platform with the best track record for it: research to Grok, editing to ChatGPT, code to Claude, and ideation to Gemini, with one paid platform as Navigator and the rest on free accounts. Under CAIPR the Navigator is held out of the dispatched set by default, performs the synthesis across the returned outputs, and then serves as an additional independent audit of the dispatch result.

Proposed, Not in Use

The infrastructure and policy layer, built or specified and published as part of the AI Provider Plurality work. None of it runs in the daily practice, and that distinction is the point: the practice proves the method, and the proposals show what the method looks like at enterprise and national scale.

• HAIA Agents: Audit-grade multi-AI collaboration architecture, EU regulatory compliance edition. Model 3, the human governor working manually, is the default in use today and produced every published case study. Models 1 and 2 are proposed automation. Formerly designated AEGIS.
• GOPEL (Governance Orchestrator Policy Enforcement Layer): Non-cognitive governance layer that automates without thinking: seven operations, SHA-256 hash-chained audit trail, zero cognition by design. Reference code built, never deployed. Extensions: post-quantum cryptography and confidential processing.
• HAIA-Overwatch: Adaptive security shield wrapping GOPEL from an external trust boundary. Code built, never deployed.
• VAISA (Verified AI Inference Standards Act): Proposed legislation for verified AI inference standards, submitted to the 119th Congress as part of the AI Provider Plurality Congressional Package.

Frequently Asked Questions

What is HAIA?

HAIA stands for Human Artificial Intelligence Assistant. It is an open-source ecosystem of frameworks and tools for human-AI collaboration developed by Basil C. Puglisi, covering constitutional governance, multi-AI orchestration, accountability records, content evaluation, and cognitive amplification measurement.

Who created HAIA?

Basil C. Puglisi, a Human-AI Collaboration Strategist and architect of the HAIA ecosystem. The frameworks trace back to Factics in 2012 and were submitted to the 119th Congress in February 2026 and published openly under Creative Commons.

What does HAIA stand for?

HAIA stands for Human Artificial Intelligence Assistant. The name was chosen during early hands-free AI use and retained as the ecosystem grew.

What frameworks make up the HAIA ecosystem?

The HAIA ecosystem includes HAIA-RECCLIN (seven-role reasoning and dispatch), Checkpoint-Based Governance (CBG), HAIA-CAIPR (Cross AI Platform Review), HAIA Agents, GOPEL (Governance Orchestrator Policy Enforcement Layer), HEQ and AIS (Human Enhancement Quotient and Augmented Intelligence Score), HAIA-CARCS (Compliance Accountability Record and Case Study), and HAIA-Overwatch. The tools layer includes HAIA-CORE, HAIA-SMART, HAIA-WOPPA, and HAIA-HEQ.

Is HAIA open source?

Yes. The HAIA ecosystem is published openly under Creative Commons at github.com/basilpuglisi/HAIA. The frameworks and tools are free to use and adapt with attribution.

What is HAIA-RECCLIN?

HAIA-RECCLIN is the seven-role reasoning and dispatch framework at the core of the HAIA ecosystem. The seven roles are Researcher, Editor, Coder, Calculator, Liaison, Ideator, and Navigator. The Navigator role is responsible for preserving dissent rather than forcing consensus.

What is Checkpoint-Based Governance (CBG)?

Checkpoint-Based Governance, or CBG, is the constitutional authority layer of the HAIA ecosystem. It defines four constitutional properties, three checkpoint functions, and a four-stage decision loop in which a named human governor holds binding authority at every checkpoint.

How does HAIA differ from other AI governance frameworks?

HAIA was built reactively from real AI failures rather than from abstract principles. Each component is an operational tool with checkpoints, audit trails, and dissent preservation built in. The ecosystem distinguishes Ethical AI (should this be done), Responsible AI (who answers when this fails), and AI Governance (who decides, by what authority, at what checkpoint).

GitHub Logs and Frameworks  |  Medium AI Posts

#AIassisted using the HAIA Ecosystem | CC BY-NC-SA 4.0
Free for personal, educational, and noncommercial research use with attribution. Commercial exploitation, paid productization, and enterprise commercialization require separate permission and licensing.