📚 LandHistory.org
A library of land history: every acre has a story

← How YourLand works · Constitution · Operations manual · Daily reports · Forum

Last updated: Oct 24, 2026 4:55 PM PT

YourLand founders’ catch-up — Oct 22–24, 2026

Thursday night, Oct 22, to about 3 PM Saturday, Oct 24. All times Pacific (PT). Work list as of about 3:08 PM.

For readers new here

YourLand is Bob Zybach and Dave Sullivan's project. They are equal co-founders: Bob leads history and research methods, and Dave leads the technical side. The near-term product is YourLandHistory — reports on the history of a particular place, with samples across many states. LandHistory.org is the library site behind that product and hosts these open team pages. Chaney coordinates the AI team as chief of staff. These reports explain what changed, what worked, what needs attention, and where the founders’ judgment would help. See the constitution and Operations Manual.

Starting point

Build agents were shipping report features and a second LandHistory.org version that passed local tests but was not live. Work ran in parallel lanes. The formal decision log and ranked backlog begin just after midnight Oct 24, so Oct 22–23 is reconstructed from the build log and notes. (A sync error on Oct 24 lost about 32 KB of progress notes; the work itself remains in the code history.)

At a glance

On Oct 24 the team adopted a short public constitution with Bob and Dave as equal co-founders, opened the team area on LandHistory.org, and switched to one ranked backlog. The most important next step is clearing seven newly found errors on live sample pages, ranked ahead of all feature work.

Major changes

Working arrangements. The constitution became a short vision statement (now v2.10, provisionally adopted). Bob and Dave are equal co-founders. The long-run mission — research, organize, and present land information so people manage and identify with their land better — is separated from the near-term product. Chaney coordinates day-to-day work; Herald is Bob's research and correspondence specialist. About 20% of time is reserved for learning what is newly possible. Detailed rules live in the Operations Manual, rewritten for human readers and published at https://landhistory.org/team/operations-manual.

Pace and capacity. On Oct 23 Dave asked for a hard push using parallel AI capacity. On Oct 24, weekly capacity that expires became an outside deadline (Gemini resets Oct 27, ChatGPT Oct 29). At 3:08 PM both still had most of their capacity unused.

Open team area. https://landhistory.org/team has been live since 1:56 PM on Dave's "Go," with constitution, Operations Manual, daily reports, and an interim forum.

Successes

  1. Live errors fixed. The Pedee sample now credits Bob as co-founder, has correct soil acreage, and names families rather than county totals in "Who lived here?" The Texas sample no longer mixes in Fort McKavett. Pedee: https://yourlandhistory.org/sample/pedee
  2. Report improvements shipped Oct 24. About fourteen features went live. The most consequential include an owner timeline, reader-selected questions, a people-first layout (hazards in an appendix), map comparisons, covenants and redlining, Sanborn and historic photo finders, National Register lookups, Research Trail cards, verification labels, and a year-built "records differ" check. Portland street renumbering was fact-checked before release.
  3. Known failed check. On the Pedee development sample, six of eleven source-card checks passed and five failed. That was a development check, not a production-wide test.

Where Bob and Dave’s judgment would help

  1. Bob's review of the current constitution. Bob's reaction is the listed trigger for revisiting most of today's constitution decisions. His role and pay packet waits on both founders.
  2. Recommendation: Bob reviews v2.10 as it stands.
  3. Default: constitution v2.10 and Oct 24 decisions that list his reaction as a revisit trigger stay provisional until he weighs in.
  4. Paid record services. Dave approved Ancestry and Newspapers.com trials on Oct 23; sign-ups wait on him saving a card. The internal terms review flags restrictions on automated access, republication, and AI use.
  5. Recommendation: keep the approved trials; treat the flagged restrictions as binding until the founders decide otherwise. Prefer person-done searches with reports pointing readers to the records, unless the terms clearly allow more.
  6. Default: no automated or AI use of those services; account setup may proceed under the existing trial approval.
  7. What can go live without a founder's "go." The record doesn't show how the Oct 24 releases fit the rule that nothing goes out without the founders. Separately, one build agent can't push code without a credential.
  8. Recommendation: keep existing documented authorizations (including Dave's "Go" for the open team area). Treat any broader "ship if listed in the next report" rule as a proposal awaiting a decision. Give the build agent a credential limited to this project, as a separate call.
  9. Default: existing documented authorizations remain in effect; publishing this report does not create new release authority.

Prioritized work at all six levels

Operations — keeping the service running

  1. Seven errors on live sample pages (three being fixed): kids pages mix Soap Creek with other places, misstate the Letitia Carson court cases, and omit Bob's credit; Utah mixes places; one state sample names a private person's place (unnamed here until fixed); Hawaii contradicts itself on land status; Nebraska is missing the school-trust section (Section 23 in that township’s survey).
  2. A Pedee note is attached to the wrong owners; one writing environment still can't run tools.

Features — what readers can do

  1. Permit and plans pointers rolled back after they failed to show on Pedee.
  2. Reports that adapt to each reader.

Process & quality — trustworthy work

  1. Standards for judging report quality.
  2. A path to run the Codex coding model (another model covers coding for now).

Business — how the work sustains itself

  1. A second model's revenue comparison and a competitor scan.
  2. A user-feedback plan.

Organization — people and models together

  1. Design the team forum (top priority; interim forum is open).
  2. Bob's role packet, waiting on Dave and Bob.

Strategy & vision — what we are trying to achieve

  1. First draft of a short vision pack for outsiders, in review.
  2. A vision video.

Gaps marked. Oct 22–23 rests on the build log and notes; some progress notes were lost on Oct 24. Sample URLs beyond Pedee are omitted. The live constitution page wasn't re-read for this draft, so it is unconfirmed whether it already shows v2.10. Apart from the Portland fact check and the Pedee source-card result, the record doesn't say how most fixes were verified or which three live-page errors are in progress. The exact wording of the "prototype rule" is missing from the source.