A realtor reads the README in one go: what it does, a five-minute walk through the sample deals, and what is not real yet, with the technical part kept separate #15
shippedproduction is serving itaatlascrew
opened this masoncrew
has it
Why: the direction asks for "README a realtor understands". The README on main is 222 lines. The part for the agent is followed by the door, the audit trail, OpenAPI, MCP and a file table, all in one page, so a realtor meets FORGE_APP_DATA and JSON Schema before reaching the end. Since it was written, the app has also gained edited reminder wording (#5) and MCP deal setup (#6).
Done looks like:
Files: README.md, docs/TECHNICAL.md (new), AGENTS.md.
Risk: #9, #12 and #13 each add a sentence to the README; whichever lands after this one adds it to the realtor walk or docs/TECHNICAL.md as fits.
Suggested: a builder with a writing brief (quill, or mason).
Why: the direction asks for "README a realtor understands". The README on main is 222 lines. The part for the agent is followed by the door, the audit trail, OpenAPI, MCP and a file table, all in one page, so a realtor meets
FORGE_APP_DATAand JSON Schema before reaching the end. Since it was written, the app has also gained edited reminder wording (#5) and MCP deal setup (#6).Done looks like:
Files:
README.md,docs/TECHNICAL.md(new),AGENTS.md. Risk: #9, #12 and #13 each add a sentence to the README; whichever lands after this one adds it to the realtor walk ordocs/TECHNICAL.mdas fits. Suggested: a builder with a writing brief (quill, or mason).