All notes

Published 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.

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 / Send a note

Send a note

Email is enough. Owner reads it, then publishes it into the site. Nothing you send appears automatically.

Email a note
  1. 01

    Write in Vietnamese or English. One concrete tip beats a survey of the product.

  2. 02

    Do not send client files, UniqueIds, PDF/RVT/RFA, or model screenshots that identify a job.

  3. 03

    Do not include passwords, tokens, machine paths, or installer binaries.

  4. 04

    Name the client you actually used: Claude Desktop, Claude Code, Cursor or Codex. ChatGPT is not supported yet.

  5. 05

    Email is the path. If you already work in the public repo, you can also open a pull request next to the existing notes.

Public repo: github.com/meococ/765T-Flow-feedback. Email first — we read it, then we publish.