<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
	<channel>
		<title>Specifications on besok</title>
		<link>https://besok.github.io/tags/specifications/</link>
		<description>Recent content in Specifications on besok</description>
		<generator>Hugo</generator>
		<language>en-us</language>
		
		
		
		
			<lastBuildDate>Sun, 08 Nov 2026 00:00:00 +0100</lastBuildDate>
		
			<atom:link href="https://besok.github.io/tags/specifications/index.xml" rel="self" type="application/rss+xml" />
			<item>
				<title>Formal Verification for the Factory Specs</title>
				<link>https://besok.github.io/posts/formal-verification-for-the-factory-specs/</link>
				<pubDate>Sun, 08 Nov 2026 00:00:00 +0100</pubDate>
				<guid>https://besok.github.io/posts/formal-verification-for-the-factory-specs/</guid>
				<description>&lt;h1 id=&#34;formal-verification-for-the-factory-specs&#34;&gt;Formal Verification for the Factory Specs&lt;/h1&gt;&#xA;&lt;p&gt;&lt;strong&gt;Summary.&lt;/strong&gt; Technical specifications for robot-cell functions live in text documents and are re-implemented by hand in the design data, the MES, the PLC, and the robot code. This causes ambiguous readings, uncovered edge cases, contradicting rules, and out-of-sync limits. I propose writing the rules once in a typed, executable rule language, analyzing them with a solver, evaluating or generating them in each system, and checking the rule version at runtime. No existing tool covers the whole chain, so the approach needs a custom framework, and a proof of concept (PoC) has to validate it first.&lt;/p&gt;</description>
			</item>
	</channel>
</rss>
