Tenuo AI introduces Jev framework for typed decisions and scoped authority

·1 views

Tenuo AI has published a blog post introducing Jev, a framework designed around typed decisions and scoped authority in software systems. The concept focuses on structuring how decisions are made and authority is delegated within applications. The post explores practical implementations of these principles to improve system design and accountability. It was shared on Hacker News, where it received minimal engagement with four points and no comments at the time of reporting.

Read the full story at Hacker News

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

Discussion (0)

Montreal passes bylaw making it illegal to insult police and city workers

The city of Montreal has adopted a new bylaw that prohibits residents from insulting police officers and municipal employees. The regulation represents a formal legal restriction on verbal conduct directed at city staff and law enforcement. The move was approved by Montreal city council, adding insults to the list of punishable offenses under local rules. The bylaw has drawn public attention and debate over its implications for free speech and civil liberties in the city.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

Key Backend Patterns to Protect Critical Business Data from Loss or Corruption

Backend systems handling payments, orders, and employee records require more than basic database storage — they must preserve history, enforce access control, and provide context when issues arise. Storing only the current state of a record leaves engineers without the audit trail needed to understand how that state was reached, making a change-history table or event-based approach far more effective. Naming business events meaningfully — such as payment_received or approval_granted — helps different services like notifications, auditing, and analytics respond appropriately to the same action. Idempotency, where the server tracks unique request identifiers to avoid duplicate processing, is essential for APIs operating over unreliable networks. Structured audit logs that record who acted, what changed, when, and on which object are also recommended as a separate layer from standard operational logs.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Build vs Buy: The Real Cost of Rolling Your Own .NET Licensing in 2026

A detailed technical guide published on DEV Community examines the true complexity and cost of building custom software licensing for .NET applications. While generating and verifying a cryptographic license key is straightforward using built-in .NET libraries, developers quickly face far harder challenges around key management, seat enforcement, and format versioning. Features like seat limits require a stateful, always-on backend service to atomically track activations, making DIY licensing effectively a separate product to build and maintain. The guide also highlights difficulties with machine fingerprinting, offline validation, and the operational burden of key rotation without breaking existing deployments. Its conclusion is that developers should only build their own licensing if needs are genuinely simple, and should consider buying a solution the moment features like trials, revocation, or customer portals are required.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

How Public-Key Signing Enables Offline Software Licensing in .NET Apps

A technical guide outlines how .NET developers can implement software licensing using asymmetric cryptography, where a private key on the server signs license payloads and a public key embedded in the app verifies them offline. The approach uses a small JSON license payload containing fields such as licensee, product tier, seat count, and expiry, all protected by an RSA signature. Developers can use the Keyright.NET SDK to initialize a single client at startup, which validates the license without making a network call, making it suitable for air-gapped or enterprise environments. The guide notes that while offline validation is fast and functional, it can be patched out by a determined attacker, and online activation should be layered on top when seat enforcement or key revocation is required.

0 comments Read more at DEV Community