# HSIMC Historical Engineering Case · From 658 Bots to MCP-Ready Capabilities

**Status:** PUBLIC HISTORICAL RESEARCH, not live MCP automation. **Date:** 2026-10-16. **Artifact:** `HRI-HSIMC-HISTORICAL-658-BOTS-TO-GENAI-MCP-READY-CASE-C0-001-20261016`.

## Research origin (2023)

658 historical concepts blended 510 occupational titles, 100 economic activity labels and 48 AI functions; generated 2023 concept images and role slogans helped articulate how generative AI might support work. These are source labels and exploratory design artifacts, not proof of 658 distinct trained models. The owner states the 2023–2025 external engineering milestones were contracted via Upwork. The milestone PDF is an exploratory dated compilation, not an itemized platform payment receipt.

## 2023–2025 development lessons

Text, voice, image, OCR and external APIs evolved into login, quotas, keys, organization and Room history; supplier listings, messaging, ERP, geographic and physical capability ideas appeared in the historical task record. Each was an experiment in making a capability accessible and reusable. Current performance/operational readiness is not inferred from an old feature list.

## 2026 public acceptance

658 e-Person and 658 Supervisor static candidate SKU pages live under `/capability-exchange/e-person-658/` (1,316 total). 655 historical AI concept images derived to WebP (approximately 24.83 MB total, versus about 2.06 GB of originals retained on Mac). Missing IDs 345, 429, 493 are skipped. No provisioning or authority granted.

## Why normalize before creating national variants

**Source:** 510 roles → 508 strict-unique role labels; 100 activities → 75 strict-unique industry labels; 48 AI functions as source records. Overall 658 → 631 distinct exact-normalized labels (25 duplicate groups, 27 surplus original occurrences). Another two editorial variants could yield 629 if reviewed. 22 proposed shared-work groups (theoretical 481 core starting templates) and 18 proposed functional primitives are not certified merged professions or trained models.

## Two independent axes

- `e-Person for X`: target work jurisdiction, legally required languages, licensing, delivery site, equipment and acceptance.
- `e-Person trained by Y`: identity and provenance of a qualified provider/reviewer, training/evaluation methodology, rights and results.
- Supervisor and execution Authority: independent controls; neither trainer locality nor target region creates automatic authority.

Treat 249 as a proposed market directory design size, **not** deployed country coverage. Do not generate 249×249 instances without accepted work demand and legal readiness.

## MCP-ready engineering recipe

1. Preserve original source record and immutable reference.
2. Define exact Work intent, inputs, outputs and acceptance criteria.
3. Separate e-Person Work executor, professional qualification and Supervisor.
4. Compose hardware, model, software and tools with an explicit capability interface.
5. Bind allowed MCP tools to a real Runtime and region-specific permissions.
6. Execute only under appropriate human Authority; capture operation identity, tests, evidence, readback and acceptance.
7. Publish outcomes and missing conditions transparently for future contributors.

An MCP interface alone does not activate equipment or create a licensed worker. Stateless model/tool invocation does not erase persistent Work state, permissions, audit or physical Reality.

## Lessons from pitfalls

- A role title is not a complete capability contract.
- Occupational roles, economic activity sectors and AI primitive functions cannot share one flat identity category.
- Historical concept art and webpage launch do not prove work delivery.
- Similar workflows can share components, but legal/safety/professional authorization remains distinct.
- Training provenance must be evidenced rather than inferred from nationality or language.
- Obsolete code need not be republished; source hashes, dated decisions, acceptance and failures make experience reusable.

## Source / evidence

See `evidence.json`. Public references:
- `https://hsimc.tech/rd/history/`
- `https://hsimc.tech/rd/engineering-continuity/`
- `https://hsimc.tech/capability-exchange/e-person-658/`
- `https://hsimc.tech/capability-exchange/e-person-658/registry.json`

No current paid sale, trainer verification, individual employment, 249-region activation or 658-MCP-server execution is claimed.