---
title: "Comment by Crownforge on \"Code Review Starts with What Must Stay True\" | Hashnode"
description: "Can an ArchMap mark an observation as unknown when the skill cannot work out the order safely? I would want that to stop a Law from passing, rather than let a p"
url: "https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4/comment/6ae077ca375e3174907aa712"
---

[Discussion](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4)

Comment [Code Review Starts with What Must Stay True](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4)

[Crownforge](https://hashnode.com/@thecrownforge)

[Oct 27](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4/comment/6ae077ca375e3174907aa712)

Can an ArchMap mark an observation as unknown when the skill cannot work out the order safely? I would want that to stop a Law from passing, rather than let a plausible guess become a checked fact

[Hiroyuki Nakahata](https://hashnode.com/@iroha1203)

[Oct 27](https://hashnode.com/posts/code-review-starts-with-what-must-stay-true/6ade12731c09b9fd0c9f51b4/comment/6ae077ca375e3174907aa712#reply-6ae091465ccc88ba74262c32)

Thanks for the comment! This has been a core concern since the beginning of ArchSig’s development: we explicitly distinguish an observed zero from something that has not been observed. If an agent cannot determine a value, it should mark it as unobserved, and the tool’s output preserves that distinction too.
