← ClaudeAtlas

flat-entrypointlisted

Use when choosing how a flat-layered service is triggered and writing the process that triggers it — one run per process started by a cron entry or a timer, a loop, a continuous stream or queue consumer, a thin HTTP wrapper, or durable execution — and deciding whether a workflow engine is earned at all; one run per process is the default, and an engine is earned only by durability across process death, retries that outlive the process, or orchestration long enough that the sequence itself must survive. Owns the framework-free function every trigger calls, the process definition that builds its dependencies once and passes them down, the retry declared where the work is invoked, the aggregate a run returns, the containment that keeps one failed run from killing a long-lived process, and where a consumer acknowledges or returns its unit, under `at-least-once-delivery`. It also carries the obligations an earned engine adds, inert under every other trigger. Testing any of it is `flat-test-entrypoint`. - Also when
wntic/pyhouse · ★ 3 · AI & Automation · score 76
Install: claude install-skill wntic/pyhouse
# Flat-Layered Entrypoint — loop vs schedule vs stream vs HTTP vs durable Covers the **process-definition** and **framework-wrapper** roles of one `flat-layered` service, whatever this service calls those packages. The shapes differ only in *what triggers a run*; the work itself is always the same functions, so switching later is a wrapper change, not a rewrite. The invariant that makes that true: **the work a trigger performs is a plain async function in a module named for that work, taking every dependency as an argument and importing no framework**, and named by `naming` for what it does. Everything in this skill is a wrapper around one of those. Every template below is one distribution: `myapp` is this service's own root package (`flat-layered`), and nothing here assumes a sibling distribution or a repository above it. ## When to use vs. neighbours - The architecture family is not settled yet — this may not be a flat-layered service at all → `architecture-choice` decides hexagonal versus flat first; everything here assumes flat. - The service's own settings and logging modules, its client and payload packages → not this skill, use `flat-layered`, which owns the role kinds and the import contract between them. - The tables, the write path and the repository class the work calls → `flat-persistence`. - Several distributions sharing one repository — the member split, the container profiles, the root task runner → `python-workspace`. One distribution on its own nee