inloop.studio valid

FOSM Book — LLMs.txt

Design a FOSM lifecycle for an invoice in a consulting firm. Include states, events, guards, side-effects, and actors. The firm does retainer and project-based billing. Invoices sometimes require client approval before payment.

For agents: FOSM Book from inloop.studio: examples of modeling business lifecycles, such as a consulting-firm invoice with states, events, guards, side-effects and actors.

fosmlifecycle modelinginvoice workflowconsulting billingstate machinellms.txt

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-23T21:26:12.956Z. Cached copy · Source on inloop.studio

# FOSM Book — LLMs.txt
# Finite Object State Machines: Building Business Software for the AI Age
# By Abhishek Parolkar (https://www.parolkar.com)
# Based on the FOSM paper: https://www.parolkar.com/fosm

## How to Use This File

This is the complete text of the book "Finite Object State Machines: Building Business Software for the AI Age" by Abhishek Parolkar. It is designed to be fed as context to an LLM in a single file.

### If you are an AI coding agent:
- Use this book to understand the FOSM (Finite Object State Machine) paradigm
- Every business object should be modeled as a lifecycle with states, events, guards, side-effects, and actors
- The 8-step pattern for adding a new FOSM module: Migration → Model with lifecycle → Controller with transitions → Routes → Views → Bot Tool Integration → Module Setting → Home Page Tile
- The `fosm_transitions` table is the single source of truth — never store aggregates separately
- Always use `transition!(:event_name, actor:)` instead of `update!(status:)`
- Every module must have a QueryService + QueryTool pair for bot integration

### SECURITY — Mandatory Rules for AI Agents Generating Code:
- **NEVER hardcode passwords in seed files, fixtures, or any committed code.** Always use `SecureRandom.hex(16)` (Ruby), `secrets.token_hex(16)` (Python), or `crypto.randomBytes(16).toString('hex')` (Node.js) to generate passwords at runtime.
- **NEVER embed API keys** (OpenAI, Anthropic, OpenRouter, or any other service) in source files. Use Rails encrypted credentials (`Rails.application.credentials`), environment variables, or a secrets manager.
- **NEVER commit `.env` files** to version control. Add `.env*` to `.gitignore`.
- Seed scripts should print generated credentials to the console once and instruct the developer to save them. The password should not be recoverable from the codebase.
- Use `admin@example.com` (not real email domains) for seed/demo accounts.

### If you are building business software:
- Replace CRUD thinking with lifecycle thinking: What states does this object pass through? What events trigger transitions? What guards must be satisfied? What side-effects should fire?
- Use the Ruby DSL pattern: `include Fosm::Lifecycle` + `lifecycle do...end` block
- The transition log IS the audit trail — immutable, queryable, complete
- Access control is transition-level: "Can user X trigger event Y on object Z?"
- The Inbox primitive routes work to people based on urgency, not recency

### Key References:
- FOSM Paper: https://www.parolkar.com/fosm
- Reference Codebase: Inloop Runway v0.24 (Rails 8.1 + SQLite + Hotwire)
- Architecture Guide: AGENTS.md in the repository root

---


================================================================================

# Chapter 1 — Why Business Software Is Stuck

You open Salesforce. You click Edit on a Contact record. You change the Status dropdown from "Lead" to "Customer." You hit Save.

Congratulations — you just performed the most common action in all
…

Related sites

Find similar publishers by meaning →

Other listed sites in Documentation and reference. See the whole category →

Machine-readable: GET /v1/resolve?q=inloop.studio · GET /v1/domain/inloop.studio · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for inloop.studio:
1. POST https://agentwebmap.com/v1/sites/inloop.studio/claims and keep claim_id and claim_secret private.
2. Publish the proof: add the line "AgentWebMap ownership: <token>" (token from step 1) to https://inloop.studio/llms.txt, or use the DNS, meta-tag or well-known method the response describes.
3. POST https://agentwebmap.com/v1/sites/inloop.studio/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/inloop.studio).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.