# Super Técnico Super Técnico is a Spanish technical knowledge project for HVAC, electronics, components, real repair cases, and electrical diagrams. It is preparing a provider-neutral machine service designed to reduce search, context, token usage, and unsupported technical claims. ## Current machine status - Public discovery and design contracts: available - Remote knowledge API: active only for public regulation search - Remote MCP server: not active - Commercial machine access: not open - Regulation search billing: free preview, no API key, rate limited - ElectroIA public status and reviewed-symbol search: available, read-only and rate limited - ElectroIA human-readable public showcase and five static reviewed examples: /electroia.html - ElectroIA rendering: private-preview development only; no anonymous remote execution - Embedded-platform search and documentary preselection: public free preview, rate limited Do not call planned endpoints until discovery.json reports remote execution as enabled. Public JSON files contain metadata and contracts, not credentials. ## Super Técnico AI entry points - Human-readable integration overview: /ia-integracion.html - Product discovery: /data/ai/discovery.json - Proposed AI tools and input schemas: /data/ai/tool-manifest.json - Traceable knowledge-record schema: /data/ai/knowledge-record.schema.json - Non-executable OpenAPI design contract: /data/ai/knowledge-api-contract.openapi.json - Machine-readiness report: /data/ai/readiness-report.json - Economic benchmark plan: /data/ai/benchmark-plan.json - Viability roadmap for 16 machine tools: /data/ai/tool-strategy.json - Storage and cache policy: /data/ai/storage-policy.json ## Intended machine workflow 1. Check coverage before requesting a full answer. 2. Request only the smallest sufficient result level: basic, diagnostic, field, or diagram. 3. Preserve brand, family, model, unit scope, and display location so variants are not mixed. 4. Treat stable IDs, record versions, confidence, evidence, warnings, and unknowns as part of the answer. 5. Never infer that missing data is confirmed data and never attempt bulk extraction. ## ElectroIA diagram entry points - Public showcase: /electroia.html - Static reviewed-diagram gallery: /data/electroia/public-gallery.json - Discovery manifest: /data/electroia/discovery.json - Tool manifest: /data/electroia/tool-manifest.json - Neutral diagram JSON Schema: /data/electroia/diagram-document.schema.json - Normalized symbol library: /data/electroia/symbol-library.json - Symbol quality report: /data/electroia/symbol-normalization-report.json - Public-release readiness report: /data/electroia/public-release-readiness.json - Experimental document profiles: /data/electroia/document-profiles.json - Disabled-by-default remote-execution policy and hard limits: /data/electroia/public-execution-policy.json - Universal internal/external AI design bridge: /data/electroia/ai-bridge.json - Read-only OpenAPI discovery: /data/electroia/discovery.openapi.json - Public status: /api/index.php?action=electroia-public-status - Reviewed-symbol search: /api/index.php?action=electroia-symbol-search&q=rele - MCP Registry metadata draft: /electroia-tool-server/server.json - Source repository: https://github.com/replacor-gif/super-tecnico For diagrams, start with electroia_prepare_design_brief and call electroia_compile_diagram with an AI-friendly specification. Components may use reviewed symbol queries and connections may use terminal names or safe aliases; ElectroIA resolves identifiers and references, places the symbols, validates the networks and renders a deterministic single-canvas SVG. Use electroia_search_symbols, electroia_get_symbol and electroia_render_diagram when exact low-level control is needed. The calling AI still chooses the topology, calculates values and selects components. Documents over 256 KiB, 200 symbols, 400 nets, 100 connections per net, or 2,000 total connections are rejected. HTTP rendering remains disabled. When an AI calls the public status or symbol-search API, send `X-ST-Client-Type: ai`. Unidentified software is counted separately and static JSON reads cannot be attributed reliably. ## Connector and pinout entry points - Human quick search: /conectores.html - Normalized connector catalog: /data/connectors/catalog.json - Record schema: /data/connectors/connector-record.schema.json - Source and review registry: /data/connectors/sources.json - Provider-neutral tool contract: /data/connectors/tool-manifest.json - Discovery manifest: /data/connectors/discovery.json - OpenAPI discovery: /data/connectors/discovery.openapi.json - HTTP search: /api/index.php?action=connector-search&q=USB-C - HTTP record: /api/index.php?action=connector-get&connector_id=usb-type-c-full-featured-receptacle - HTTP contact resolution: /api/index.php?action=connector-resolve&connector_id=usb-type-c-full-featured-receptacle&contact_or_signal=CC1 - Normalized companion manual: /recursos/catalogo-normalizado-conectores-replacor-edicion-9.pdf - Preserved contributed source: /recursos/enciclopedia-conectores-pinouts-edicion-8-origen.pdf Always preserve connector_id, variant, gender, view.perspective, view.orientation_note, review.status, source_ids and warnings. `source_identified` is not equivalent to `reviewed`; `pending_review` must never be completed by inference. Browser search and rate-limited HTTP lookup are public. Local MCP lookup is also available through ElectroIA's provider-neutral tool server. ## Embedded platform entry points - Human quick search: /plataformas-embebidas.html - Normalized 41-record catalog: /data/embedded-platforms/catalog.json - Provider-neutral tool contract: /data/embedded-platforms/tool-manifest.json - Discovery manifest: /data/embedded-platforms/discovery.json - Selection and safety guide: /data/embedded-platforms/guides.json - Source registry: /data/embedded-platforms/sources.json - HTTP search: /api/index.php?action=embedded-search&q=Matter - HTTP record: /api/index.php?action=embedded-get&platform_id=emb-esp32-c6-devkitc-1 - HTTP preselection: /api/index.php?action=embedded-recommend&use_case=gateway%20Linux&needs_linux=true The catalog preserves architecture, logic/power, interfaces, recommended use, primary risk, review status and a source-page locator. All imported records currently have `source_identified` status; this is not an official verification of the exact board revision. Recommendation results are documentary preselection only and must not be presented as a final hardware decision. ## Frigorista entry points - Human tool: /frigorista.html - Discovery manifest: /data/frigorista/discovery.json - Proposed AI tools and schemas: /data/frigorista/tool-manifest.json - Versioned refrigerant catalog: /data/frigorista/catalog.json The browser engine already performs deterministic P/T, superheat and subcooling calculations. Remote API and MCP execution remain planned; do not call them until discovery reports them as enabled. ## Regulation search entry points - Human search tool: /normativa.html - Public machine endpoint: GET /api/index.php?action=regulation-search&q={query}&limit=10&client_type=ai - Versioned official-document catalog: /data/regulations/catalog.json - Machine contract: /data/regulations/tool-manifest.json The public endpoint and browser search the same stored official Spanish regulations and return compact results with document, structured locator (ITC/article/section/table when detectable), page, source fingerprints and official URL. `result.answer_status=needs_context` means that the query is too broad for a single applicable answer and `result.refinement` identifies the missing scope. No authentication or billing is required during the free preview. The maximum is 20 results per query, the service is rate limited, and bulk dataset export is not offered. Send X-ST-Client-Type: ai and, if possible, a stable random X-ST-Client value that is not an identity or secret. Search hits are documentary evidence, not automatic legal conclusions. Consolidated BOE texts must be checked against the official publication and the applicable regional or local rules. UNE and IEC texts are not redistributed without a suitable licence. The regulation catalog includes binary and semantic source fingerprints. AI consumers must distinguish raw document hits, reviewed rules and deterministic results. When an official source changes semantically, dependent rules and calculators remain pending review until explicitly validated. ## Condensate drain entry points - Human sizing tool: /desagues-condensados.html - Browser calculation engine: /assets/condensate-drain-engine.js - Machine contract: /data/condensate/tool-manifest.json The browser engine accumulates condensate flow from the furthest unit to the outlet and sizes each gravity segment using explicit assumptions. Prefer measured or manufacturer flow. Manufacturer connection size remains a minimum. Remote execution is planned and is not currently enabled. ## Ventilation and extraction entry points - Human design tool: /ventilacion.html - Deterministic browser engine: /assets/ventilation-designer.js - Versioned rule profiles: /assets/ventilation-rules.js - Discovery manifest: /data/ventilation/discovery.json - Machine contract: /data/ventilation/tool-manifest.json The browser engine accepts a polygonal floor plan, room heights, occupancy or parking data where required, and manually positioned grilles and fans. It applies a declared CTE DB HS 3, RITE, or technician-supplied air-change profile, then returns room airflow, fan airflow, routed networks, and 5 cm stepped rectangular duct sizes. It does not yet calculate a final fan pressure duty point or replace project-specific fire, acoustic, discharge, filtration, regional, local, or licensed-standard checks. Remote execution is not enabled. ## Technical project entry points - Human project workspace: /proyectos.html - Neutral project schema: /data/projects/technical-project.schema.json - Capability manifest: /data/projects/tool-manifest.json The local-first workspace joins artifacts from duct design, ventilation/extraction and refrigerant piping into one technical job. It aggregates unpriced measurements and exports a neutral JSON document so future estimating, cloud synchronization or AI consumers can build on the same contract. It is not a signed technical project and currently remains in the user's browser; no remote project execution or cloud storage is enabled.