Changelog
Live

Pin a fact subtype to a block over the API and MCP

Blocks can now be pinned to a subtype so every fact written into them gets that type, settable over REST, MCP and the assistant, for builders shaping their fact layer.

Until now the classifier decided each fact's type on its own. A block had no way to say that everything written into it is a particular kind of fact, so a block built for one subject could still collect facts classified as something else.

What's new

  • Pin a subtype when you create a block or stack. add_block and create_stack over MCP, addBlock and addStack in the assistant, and POST /v1/stacks over REST now take an optional subtype.
  • It sets the type ahead of the classifier. A pinned subtype is stored on the block as configuration.subtype and sets the type sent to the classifier, so every fact in that block carries it.

Why it matters

When you are building a stack where every block has a known shape, pinning the subtype keeps the classification predictable instead of leaving it to be inferred fact by fact. The block declares what it holds, and the facts you write into it inherit that.

Where to find it

The subtype parameter is documented alongside the stack and block endpoints at api.getnoan.com.