One binary: the lint and the trainer are commands of portal
Test / test (pull_request) Successful in 1m7s
Test / test (pull_request) Successful in 1m7s
portal serve runs a site; portal lint is what iris was; portal plan, build, report and the rest are what portal-trainer was. One source at one version, so the three never disagree about what content means. Both histories are merged in (subtree). The release attaches the bare binary for a content repo's CI. The trainer's plans, intakes, engines and reference prompt come along; its runs stay in the old repo. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GT37Z1Xtfd9pUuQtMTg6Yt
This commit is contained in:
co-authored by
Claude Fable 5.1
parent
d0d1cbf23d
commit
96b3746643
@@ -0,0 +1,38 @@
|
||||
# An intake as the owner of a machine hire yard would fill it in.
|
||||
business: Fjellstad Hire
|
||||
contact: { name: Ola Fjellstad, email: ola@fjellstadhire.example }
|
||||
language: en
|
||||
|
||||
what_we_do: >
|
||||
We hire out machines: mini diggers, lifts, compactors, generators,
|
||||
that kind of thing. A counter with two people, a yard with three who
|
||||
deliver, collect and fix, and me in the office doing accounts and
|
||||
the business customers.
|
||||
|
||||
who_comes_to_us: >
|
||||
Private people who need a machine for a weekend and have often never
|
||||
driven one. Building and landscaping firms who need something on a
|
||||
site from a date for a period. Anyone whose hired machine has
|
||||
stopped working while they have it. Firms who hire often and want
|
||||
an account so they can send anyone to collect and get one invoice a
|
||||
month.
|
||||
|
||||
what_we_keep_track_of: >
|
||||
Hires: someone asks, the counter reserves it, the yard hands it out
|
||||
or delivers it, and the yard takes it back. Some are cancelled
|
||||
before they go out.
|
||||
Breakdowns: a machine stops during a hire; the yard takes it on and
|
||||
either fixes it on site or swaps it.
|
||||
Account applications: a firm applies, I check the company and its
|
||||
credit, and it is approved or turned down.
|
||||
Damage on return: the yard finds damage when a machine comes back; I
|
||||
either invoice the customer or write it off.
|
||||
|
||||
who_is_involved: >
|
||||
The counter handles hires. The yard handles breakdowns and the
|
||||
handing out and taking back. The office does accounts and damage.
|
||||
|
||||
what_slows_us_down: >
|
||||
The yard finds out about breakdowns from whoever picks up the phone.
|
||||
Damage found on return is written on a whiteboard and half of it is
|
||||
never invoiced.
|
||||
Reference in New Issue
Block a user