Operations

What changed in the technical base

This refactor reorganized the project so the main site, documentation and the serverless layer share a single operational story. VitePress config, shared data, exports and dossiers now move together.

Operational principles

Content driven by data

The same shared catalog powers site, APIs, exports and derived pages, reducing drift between narrative, runtime and operations.

SEO and distribution

Robots, sitemap, schema.org, llms.txt, PWA and public channels work together to reinforce discovery and distribution.

Auditable API

Small routes with request metadata, explicit filters and predictable payloads make discovery, troubleshooting and automation simpler.

Predictable operations

Scripts, health checks, matrix checks, local Docker and documented commands make evolution less fragile and more repeatable.

Operational dossiers

Operations

Flows, quality gates and links between runtime and narrative.

Each operational dossier links routes, stacks, categories and projects to make the base easier to read and less abstract.

Export JSONOperations endpoint

Operational dossier

3 projects

Content driven by data

The same shared catalog powers site, APIs, exports and derived pages, reducing drift between narrative, runtime and operations.

Signals

• central catalog reused by theme, workbench, discovery and exports
• deterministic public artifacts generated before dev, test and build
• dossiers and filters derived from the same canonical inventory

Quality gates

• npm run site:export
• npm test
• npm run build

Open dossierInspect payload

Operational dossier

3 projects

SEO and distribution

Robots, sitemap, schema.org, llms.txt, PWA and public channels work together to reinforce discovery and distribution.

Signals

• sitemap and structured metadata published together with the build
• llms.txt, robots.txt and main routes aligned to an auditable inventory
• main site, supporting portal and technical profile reinforcing the same positioning

Quality gates

• npm run site:export
• npm run build

Open dossierInspect payload

Operational dossier

3 projects

Auditable API

Small routes with request metadata, explicit filters and predictable payloads make discovery, troubleshooting and automation simpler.

Signals

• request_id, timestamp, path, method and query in every envelope
• simple filters that avoid fetching full payloads when unnecessary
• endpoints and exports reflecting the same catalog state

Quality gates

• npm run site:export
• npm test

Open dossierInspect payload

Operational dossier

4 projects

Predictable operations

Scripts, health checks, matrix checks, local Docker and documented commands make evolution less fragile and more repeatable.

Signals

• runtime commands versioned inside the project
• short and composable quality gates validating the official path
• readiness considered by stack, project and operation

Quality gates

• npm run site:export
• npm run format:check
• npm run lint
• npm test
• npm run build
• npm run matrix:check

Open dossierInspect payload

Local pipeline

Quality gates

Minimum flow to evolve safely

• npm run site:export
• npm run format:check
• npm run lint
• npm test
• npm run build
• npm run matrix:check

Minimal and auditable API

Each API response returns an envelope with request_id, timestamp, method, path, query and an explicit payload. That makes troubleshooting and automation easier without depending on implicit logs.

GET

/api/health

Operational status and request metadata.

GET

/api/openapi.json

Contrato OpenAPI 3.1 da camada publica e auditavel.

GET

/api/v1/openapi.json

Alias versionado do contrato OpenAPI para integracoes e tooling.

GET

/api/profile

Institutional summary with channels and specialties.

GET

/api/links

Catalog of public links for the brand and personal account.

GET

/api/catalog

Shared catalog powering the site and public layer.

GET

/api/audit

Snapshot of counts, routes, surfaces and public exports.

GET

/api/discovery

Flat inventory of public resources for filters, automation and exploration.

GET

/api/portfolio

Filterable snapshot of portfolio cases, stacks, categories and signals.

GET

/api/categories

Thematic directory by category with signals, stacks, capabilities and related operations.

GET

/api/categories/:slug

Deep category dossier with portfolio, projects, capabilities and related operations.

GET

/api/capabilities

Capability domains, technologies and delivery modes of the lab.

GET

/api/stacks

Map of recurring technologies with links between portfolio and capabilities.

GET

/api/stacks/:slug

Deep stack dossier with related projects, useful commands and operations.

GET

/api/projects

Filterable directory of technical and operational project dossiers.

GET

/api/projects/:slug

Details of a specific dossier with relations, commands and surfaces.

GET

/api/operations

Operational dossiers with quality gates, routes, stacks and related projects.

GET

/api/operations/:slug

Detailed operational dossier for deeper reading by flow.