Todas las notas

Publicado 765TPlaybookMCP

The BIM knowledge library is off by default

We keep a BIM knowledge library as a product asset. It is not switched on in the default runtime. What runs today is the execution gate — preview, authorize, execute, verify.

Esta nota está en inglés por ahora.

What the library is

Context Engineering Flow names four layers of context. The knowledge library sits with the action gate as a product asset we maintain — playbooks, API judgement, which compiled tool to reach for. That is a library, not a claim that a private engine is already answering every job.

Why it does not answer by default

The knowledge half is behind a configuration flag, and the shipped default leaves that flag off. A clean install therefore runs without the knowledge search provider. Turning it on is an Owner decision, not something the website can promise as the out-of-the-box path.

What still runs today

The other half of that layer — the preview, authorize, execute, verify gate — is on the live path and does not depend on the knowledge flag. Brief the agent with the outcome, the open model, and your office rules. Do not expect a knowledge search to fire unless you have been told that flag is on for your machine.

02 / Enviar una nota

Enviar una nota

Un correo basta. El Owner la lee y después la publica en el sitio. Nada aparece solo por enviarlo.

Enviar correo
  1. 01

    Escribe en español, en vietnamita o en inglés. Un consejo concreto vale más que un resumen del producto.

  2. 02

    No envíes expedientes de cliente, UniqueIds, PDF/RVT/RFA ni capturas que identifiquen un encargo.

  3. 03

    No incluyas contraseñas, tokens, rutas de máquina ni el instalador.

  4. 04

    Indica el cliente de IA y la versión exactos que utilizaste. No deduzcas compatibilidad del producto por una etiqueta MCP.

  5. 05

    El correo es el camino. Si ya trabajas en el repositorio público, también puedes abrir un pull request junto a las notas existentes.

Repositorio público: github.com/meococ/765T-Flow-feedback. Primero el correo: lo leemos y después lo publicamos.