SShortSingh.
Back to feed

SAFi Framework Proposes Deterministic Control Layer to Govern LLM Behavior

0
·1 views

A developer perspective published on DEV Community argues that mainstream AI governance tools are taking the wrong approach by keeping LLMs in control of their own execution. The author contrasts tools like Claude Code, where the LLM drives decisions autonomously, with SAFi, a framework that treats the LLM as just one component within a deterministic pipeline. In SAFi, any action proposed by the LLM must be approved by a separate, rule-based Python module that cannot reason independently. The execution loop consists of five stages, with LLMs invoked in only two of them where semantic reasoning is genuinely needed. The author contends that this architecture delivers the predictability that enterprise IT environments require from AI systems.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Valkey 9.1 and Redis 8.4 Have Diverged Enough to Demand a Real Choice

When Redis changed its license in March 2024, most teams adopted a wait-and-see approach toward Valkey, the Linux Foundation fork that was initially little more than Redis 7.4 under different governance. By mid-2026, both projects have shipped major releases with features the other lacks, making the choice a genuine technical decision rather than a governance preference. Valkey 9.1 introduces hash field-level expiration, database-scoped ACLs for multi-tenancy, optional Lua module removal for reduced attack surface, and significant memory and throughput improvements including 2.1 million requests per second on a single node. Redis 8.4, which went GA in November 2025, counters with fused full-text and vector search capabilities suited to AI-driven workloads, positioning it as the stronger platform for use cases beyond pure caching. Experts now suggest the right choice depends on workload characteristics, with Valkey favoring high-throughput cache-first deployments and Redis better serving applications requiring advanced search and data-structure features.

0
ProgrammingDEV Community ·

Developer Technique: Using HTML Output Files to Make AI Coding Agent Results Readable

Software developer Eivind Kjøsbakken published an article on Towards Data Science on September 10, 2026, describing a productivity technique he uses roughly 100 times per day when working with AI coding agents like Claude Code. He identified two core problems with standard terminal output: important information is scattered throughout a conversation with no visual hierarchy, and plain text is cognitively harder to process than formatted content. His solution is to instruct the AI agent to compile key results into an HTML file and open it automatically in a browser, enabling headers, bold text, highlights, and diagrams that reduce reading effort. He implements this permanently by editing a user-level Markdown configuration file so the instruction applies to every session without retyping. For complex reporting tasks, he also uses specialized skill sets such as a test-report template and an architecture-diagram tool called Archify, which generates SVG-based diagrams inside HTML files.

0
ProgrammingDEV Community ·

ICANN Weighs Policy Shift to Target Entire Abuse Domain Portfolios, Not Just Single Domains

Since April 2024, ICANN's Registrar Accreditation Agreement has required registrars to investigate and mitigate only the specific domain named in an abuse complaint, resulting in over 25,000 domains actioned across nearly 530 investigations. Critics argue this one-domain-at-a-time model fails to address coordinated abuse campaigns, which typically operate across portfolios of dozens or hundreds of domains registered through shared accounts or identities. ICANN's DNS Abuse Small Team identified this accountability gap as a top priority in late 2025, noting that mitigating a single domain leaves the broader operation intact. In response, a working group established under a GNSO Council charter adopted in January 2026 is developing a proposal called Associated Domain Checks, which would require registrars to evaluate other domains linked to a confirmed abuser via defined signals. As of mid-2026, the group remains divided on key questions, including what threshold should trigger such checks and whether they must occur before or after the initial domain is mitigated.

0
ProgrammingDEV Community ·

Small product site bars Amazon as a data source to separate affiliate links from specs

A developer running Inch & Drawer, a kitchen organizer fit-checker, built a data pipeline rule that blocks Amazon listings from supplying product dimensions, reserving that role for manufacturer pages and retailer listings that print measurements directly. The decision was driven by a conflict-of-interest concern: Amazon links on the site earn affiliate commissions, so allowing them to also vouch for accuracy would mix two incompatible functions. A generator bug was discovered when a fallback mechanism accidentally assigned an Amazon brand storefront URL as a primary source, which a catalog test caught and prompted a stricter assertion that now fails loudly if any Amazon domain appears as a source. A separate timezone bug caused records checked in Korea to appear future-dated during a UTC midnight-to-9am window, fixed by storing full timestamps with UTC offsets. A third issue saw a measurement note copied verbatim into a value field, resolved by storing only the printed figure and moving the surrounding text to an evidence field.