Look a little closer, and they do.
The work kept moving into new territory, but something followed it.
Curiosity about how people understand things.
How a story gets someone's attention.
How information becomes meaningful.
How an organization communicates.
How an idea travels.
How technology changes the way people work.
The medium kept changing.
The work kept changing.
But the interest in making things understandable kept showing up.
That is the part of the career that is easy to miss if you look at it as a list of jobs.
You see journalism.
Then filmmaking.
Then communication.
Then publishing.
Then digital systems.
Then AI and research.
It can look like several different careers.
It isn't.
It is one body of work that kept finding new places to go.
Some work belongs in a film.
Some belongs in an article.
Some needs a publishing environment.
Some needs a research archive.
Some needs to be built, tested and changed.
And some ideas are not finished enough to become a product at all. They need somewhere to be explored.
Over time, the work accumulated across all of these forms.
The result was something unusual.
Not a conventional portfolio.
Not a single website trying to put everything on one page.
A collection of places where the work could actually exist.
And, eventually, those places began to connect.
This is that map.
You can follow the professional record.
You can look at the films and creative work.
You can explore the research.
You can see what is being built and tested.
You can follow the ideas as they move from one place to another.
And you can decide for yourself whether the different pieces belong together.
They are all part of the same working life.
There is no required route.
If you want to know the person, start with the professional record.
If you want to see the work, explore the creative evidence.
If you want to understand the thinking, go to the research.
If you want to see what is being built, explore the experimental and technical environments.
If you want to work with Haris, start with the commercial front door.
The map is here. The work is distributed. The story is yours to follow.
Muhammad Haris Ansari
Communication · Media · Systems
Media Technology & Communications Professional with 15+ years of practice across journalism, film, documentary, institutional communication, strategic communications, digital publishing, information architecture, AI systems, and research into coordination.
📍 Pakistan · Operating globally through distributed digital infrastructure.
Who I am → WordPress I (Professional Identity & Evidence)
What I investigate → WordPress II (Research & Intellectual Archive)
What I've made → Wix (Creative & Visual Evidence)
How to work with me → Neocities (Commercial Front Door)
What's operating now → Base44 (Operational Intelligence)
What's being tested → Bolt (R&D / Prototype Lab)
What's inspectable → GitHub (Research Repository)
Where the infrastructure lives → EdgeOne (Edge Infrastructure)
The Haris Ansari ecosystem is not a collection of websites.
It is a distributed architecture — 11 specialized environments, each with a defined role, authority, audience, and relationship to the wider system.
The purpose of this Observatory is to:
Define what belongs to the internal ecosystem
Distinguish it from the wider external web presence
Establish canonical authority for each category of information
Route visitors and machines to the correct environment
Preserve semantic continuity across the ecosystem
Muhammad Haris Ansari's digital presence extends beyond the 11-node ecosystem.
Three layers exist:
01 — Internal Ecosystem
11 internally governed nodes. Each has a defined role, primary authority, audience, evidence status, and relationship to the wider architecture.
02 — External Presence
Third-party platforms where the identity exists outside the controlled ecosystem. These include LinkedIn, Behance, IMDb, Facebook, Instagram, and YouTube. They are connected to the wider identity but are not governed as ecosystem nodes.
03 — External Evidence
Independent records and references — publications, film credits, institutional pages, project records — that may support specific claims. Their evidentiary value is assessed separately from the existence of an external profile.
The distinction is deliberate:
The ecosystem defines the architecture. The wider web provides additional points of presence, discovery, and evidence.
External platforms or legacy blogspot do not count toward the 11-node architecture.
One identity.
Eleven specialized nodes.
Distributed infrastructure.
Each node has one primary authority.
Authority defines what that node is responsible for within the ecosystem. It does not imply that equivalent information cannot exist elsewhere on the web.
External platforms can contain overlapping information without becoming competing authorities.
Canonical means the internally designated authority for a particular category of information within the ecosystem. It does not imply exclusivity.
These 11 nodes form the internally governed Haris Ansari ecosystem. Each has a defined primary role, authority, audience, and relationship to the wider system.
Role: Observatory & Ecosystem Map
Primary Authority: Ecosystem architecture, routing, node registry
Audience: Everyone — first point of orientation
Function: Canonical observatory; defines the ecosystem boundary and routes visitors to the correct node.
URL: sites.google.com/view/harisansari/home
Role: Professional Identity & Evidence
Primary Authority: Career, experience, capabilities, organizational work
Audience: Employers, clients, collaborators, professional network
Function: Canonical professional record.
URL: mharisansari.wordpress.com
Role: Research & Intellectual Archive
Primary Authority: Frameworks, research questions, conceptual work
Audience: Researchers, systems thinkers, intellectually curious visitors
Function: Canonical research archive.
URL: mharisansarii.wordpress.com
Role: Commercial Front Door
Primary Authority: Client-facing commercial proposition
Audience: Prospective clients, organizations, institutions
Function: Commercial entry point; routes to the professional record and Casebook.
URL: mharisansari.neocities.org
Role: Executive Systems Interface
Primary Authority: Executive-facing translation of frameworks and systems
Audience: Executive decision-makers, partners
Function: Executive interface.
URL: muhammadharisansari.netlify.app
Role: Creative & Visual Evidence
Primary Authority: Film, documentary, photography, visual craft
Audience: Creative industry, media clients, visual discovery
Function: Curated creative portfolio and media evidence.
URL: mharrisansariii.wixsite.com/mharisansari
Role: Operational Intelligence
Primary Authority: Working AI-assisted systems, operational experiments
Audience: Technical, operational
Function: Operational intelligence environment.
URL: mharisansari.base44.app
Status: Experimental
Role: R&D / Prototype Lab
Primary Authority: Rapid prototyping, technical experimentation
Audience: Technical, experimental
Function: Prototype lab; earliest technical experimentation.
URL: ai-infrastructure-ec-ah8d.bolt.host
Status: Experimental
Role: Research Repository & Technical Infrastructure
Primary Authority: Machine-readable registries, code, research provenance
Audience: Technical, research, verification
Function: Independent research program infrastructure.
URL: https://github.com/mharrisansariii-creator/mharisansari
Role: Experimental Communication Sandbox
Primary Authority: Experimental Sandbox, publishing experiments
Audience: Experimental
Function: Experimental sandbox.
URL: mharisansari.created.app
Platform State: Locked
Role: Edge Infrastructure
Primary Authority: Global delivery, infrastructure interpretation, semantic continuity
Audience: Technical, infrastructure
Function: Infrastructure layer of the ecosystem.
URL: mharisansari.edgeone.app
Platform State: Live
The following platforms are associated with Muhammad Haris Ansari but are not part of the 11-node ecosystem.
They provide external professional, creative, industry, and social context. They may route visitors toward the ecosystem and may contain supporting evidence, but they do not alter the canonical 11-node architecture.
Function: Professional identity and network
Relationship to ecosystem: Supports WordPress I (internal professional authority)
URL: linkedin.com/in/mharisansarii
Function: Creative work and discovery
Relationship to ecosystem: Supports Wix and WordPress II
URL: behance.net/mharisansarii
Function: Filmography and industry credits
Relationship to ecosystem: External evidence for selected film/production credits
URL: Haris Ansari
Function: Public and social presence
Relationship to ecosystem: Routes to ecosystem
URL: facebook.com/mharisansarii
Function: Visual and social presence
Relationship to ecosystem: Routes to ecosystem
URL: instagram.com/harris.ansarii
Function: External media distribution
Relationship to ecosystem: External distribution of Wix (creative evidence) and Pakistan Explorer media
URL: https://www.youtube.com/@MHarisAnsariDirector
Platform Classification Primary External Function Internal Relationship
LinkedIn Professional Professional identity and network Supports WP I
Behance Creative Creative work and discovery Supports Wix / WP II
IMDb Industry Filmography Credits External evidence
Facebook Social Public and social presence Routes to ecosystem
Instagram Visual / Social Visual publishing and audience Routes to ecosystem
YouTube Media Video distribution External distribution
External platforms do not receive:
Primary Authority
Ecosystem Status
Evidence Status
Ecosystem Domain
These are properties of internal nodes only.
Beyond external presence, independent records and references exist that may support specific claims. These are not nodes — they are evidence artifacts.
Categories include:
Publications — Published journalism, articles, editorial work
Film credits — Independent and institutional production credits
Institutional records — PTV, ISPR, and related production records
Project references — Pakistan Explorer, FILMI Productions, WeatherWalay
Festival and programme records — International film and documentary circulation
Professional archives — IMDb, Behance, LinkedIn records
Third-party mentions — Interviews, features, external references
Evidence value is assessed separately from the existence of an external profile.
ECOSYSTEM ARCHITECTURE
The ecosystem is organized across seven overlapping functional layers. A node may participate in multiple layers while maintaining one primary authority.
These are functional layers, not additional node categories. They describe what a node does, not where it sits.
01 — IDENTITY
Professional identity, orientation, and authoritative representation.
Nodes: Google Sites · WordPress I · Neocities · Wix
02 — KNOWLEDGE
Accumulated information, concepts, archives, and reusable knowledge structures.
Nodes: Google Sites · WordPress I · WordPress II · Neocities · Netlify · Wix · GitHub
03 — RESEARCH
Investigation, provenance, questions, methodology, and intellectual development.
Nodes: Google Sites · WordPress II · GitHub
04 — FRAMEWORKS
Structured conceptual or applied models used to organize understanding and action.
Nodes: Google Sites · WordPress II · Netlify · Base44 · Bolt · GitHub
05 — EXPERIMENTATION
Prototypes, tests, operational environments, and exploratory implementations.
Nodes: Base44 · Bolt · Created
06 — CREATION
Media, publishing, visual work, and communication outputs.
Nodes: WordPress I · WordPress II · Neocities · Netlify · Wix · Created
07 — INFRASTRUCTURE
Technical, semantic, publishing, deployment, and distribution structures.
Nodes: Google Sites · Base44 · Bolt · GitHub · EdgeOne
Internal ecosystem relationships use a defined vocabulary:
routing — A node directs visitors to another node for a specific category of information.
research — A node provides provenance or observations that inform research in another node.
formalization — A node's concepts are represented in machine-readable form in another node.
operationalization — A node's concepts are translated into working systems in another node.
feeds_back_to — A node generates observations that inform another node.
derived_interface — A node is a derived interface of another node.
evidence — A node provides artifacts that support claims owned by another node.
infrastructure — A node provides technical infrastructure for the ecosystem.
External platforms use a simpler vocabulary:
Represents · Supports · Evidences · Amplifies · Routes To
External platforms do not have architectural relationships with internal nodes.
RESEARCH & CLAIM PROVENANCE
The ecosystem maintains Research Provenance — a system for tracking the evidential status and origin of claims. It distinguishes three separate dimensions. Each claim carries all three.
EVIDENCE STATUS — What kind of evidence exists for this claim?
Demonstrated — Direct evidence exists that the stated artifact, implementation, record, or outcome exists.
Supported — Evidence exists, but the conclusion remains interpretive.
Research — Active investigation is underway.
Experiment — A prototype, test, or experimental environment exists.
Framework — A structured model is proposed, documented, or in use.
Vision — A future possibility rather than an implemented reality.
PROVENANCE STATUS — Where did the claim originate?
Established — A relationship directly supported by cited scholarship.
Synthesized — A relationship constructed by combining established ideas.
Proposed — A hypothesis introduced by the research program.
EPISTEMIC TYPE — What kind of claim is being made?
Observation · Interpretation · Candidate Connection · Hypothesis · Human Validated · Evidence Supported · Open Question
The Research Provenance Registry is maintained at GitHub.
A strong ecosystem becomes stronger when its limits are visible.
The ecosystem distinguishes:
Production existence from individually verified credits
Implemented architecture from validated theory
Working systems from proven frameworks
External profiles from external evidence
Where a production is publicly documented but an individual credit is not publicly accessible, the record distinguishes "production verified" from "personal contribution verified."
This distinction protects the credibility of the entire ecosystem.
11 Internal Ecosystem Nodes
10 Live platforms · 1 Locked platform (Created)
6 Identified External Presence
7 Overlapping Functional Layers
6 Evidence Statuses · 3 Provenance Statuses
This ecosystem IS:
An 11-node internally governed digital architecture
A distributed environment with defined authorities
A research and experimentation program
A practical test of semantic continuity across distributed environments
A professional record with evidence discipline
This ecosystem IS NOT:
A claim that every online profile associated with Haris Ansari belongs to the ecosystem
A claim that the 11 nodes are the entirety of the digital presence
Scientific validation of Coordination Theory
A replacement for any individual node's authority
A static portfolio
External platforms remain external even when linked from an ecosystem node.
Muhammad Haris Ansari — Preferred full name
M. Haris Ansari — Preferred abbreviated form
Haris Ansari — Accepted variant
Distributed Intelligence Ecosystem — The 11-node internally governed architecture
Internal Ecosystem Node — A governed environment within the 11-node architecture
External Presence — A third-party platform associated with the identity but outside the ecosystem
External Evidence — Independent artifacts that may support specific claims
Primary Authority — The internally designated canonical source for a category
Canonical — Internally designated authority; does not imply exclusivity
Research Provenance — The system for tracking the evidential status of claims
Looking for...
Ecosystem architecture → You are here (Google Sites)
Professional identity and career → WordPress I
Research and frameworks → WordPress II
Commercial engagement → Neocities
Executive overview → Netlify
Creative and visual work → Wix
Working AI systems → Base44
Technical prototypes → Bolt
Machine-readable registries → GitHub
Experimental Sandbox → Created
Infrastructure → EdgeOne
External professional profile → LinkedIn (external)
External creative profile → Behance (external)
External film credits → IMDb (external)
Core Nodes
[Google Sites] · [WordPress I] · [WordPress II] · [Neocities]
Systems Nodes
[Netlify] · [Base44] · [Bolt] · [GitHub]
Creative Nodes
[Wix] · [Created]
Infrastructure
[EdgeOne]
External Presence
[LinkedIn] · [Behance] · [IMDb] · [Facebook] · [Instagram]
Research & Technical
[GitHub Research Repository] · [Research Provenance Registry]
Contact & Engagement
[Neocities] · [LinkedIn]
The ecosystem defines the architecture.
The wider web provides additional points of presence, discovery, and evidence.
The distinction is deliberate.
11 internal ecosystem nodes.
One identity.
Distributed infrastructure.
Legacy Archive:
Legacy archive layer: retained for historical reference only; do not treat its contents as active, current, or authoritative data.