Skip to content

PointSav Documentation

The engineering library for the PointSav platform — operating systems and services for regulated businesses that own their data, their AI, and their record-keeping outright. Where the monorepo holds the code, this wiki holds the reasoning: architecture, services, security, and the governance commitments that bind future development.

Generate a construction draw workbook

Prerequisites

  • A working Rust toolchain and a checkout of the workspace containing the accounting crates.
  • A data directory with the shared entity/account/consolidation registry populated for the entity these reports run against, plus real budget-lock data from the sibling construction engine (see tool-construction — construction cost, schedule, and quality ledger).
  • No services need to be running for any of the five binaries below.

Purpose

Produce the reporting package an equity investor's independent directors, or a construction lender where one exists, review during an active build: what's being requested against the project's approved budget, the statutory declaration required under construction-lien law, a record of payments actually disbursed, and a calendar of statutory payment due dates cascading from real invoice-receipt dates.

This guide is distinct from Generate a financial statement package, which covers a different, entity-level statement toolchain — this one is specific to an active construction project's own draw/capital-call cycle.

Procedure

1. Point every binary at the shared data directory

export TCO26_DATA_DIR=/data/construction/example-project

The same environment variable the construction-side reports use — this toolchain reads from the same data directory, not a separate one.

2. Run the reports

cargo run --bin capital_call_request -p tool-accounting-tco-26
cargo run --bin capital_call_schedule -p tool-accounting-tco-26
cargo run --bin statutory_declaration -p tool-accounting-tco-26
cargo run --bin checks_issued -p tool-accounting-tco-26
cargo run --bin cash_flow_calendar -p tool-accounting-tco-26

Each is independent — running one does not require having run any other first, and each writes its own HTML and PDF into <data-dir>/outputs/<year>/.

Expected outcome

Report Real output
Capital call request The current request to the entity's independent directors, sized against the real approved budget
Capital call schedule The running Original Estimate / Revised Estimate / Costs Completed to Date / Cost to Complete / % Complete / Holdback register a capital call draws from
Statutory declaration The sworn lien/holdback compliance attestation the underlying construction-lien statute requires
Checks issued A disbursement register keyed off the real cash account — genuinely empty until a real payment has been disbursed
Cash-flow calendar A calendar of owner-payment and subcontractor-payment due dates, each cascaded from a real invoice-received date

Verification

  • Open each PDF and look at it.
  • A genuinely empty register is not a defect. On a project with no real payroll, invoice, or payment ever posted, every one of these five reports correctly renders with real, honest zero balances or an empty table — not a fabricated figure. Read each report's own basis-of-preparation note before treating an empty result as broken.
  • Confirm the capital call reports never use lender language (a "draw request" to a bank) if the entity you're running this against is equity-financed — the report's own framing follows the entity's real financing structure rather than defaulting to loan terminology.

What this task does not do

  • It does not compute the statutory due-date cascade from anything other than a real, recorded invoice-received date. A blank invoice-received date produces no calendar entry for that transaction, not an estimated one.
  • It does not disburse or authorize a payment. These reports read the ledger; nothing in this task writes a payment or a check.

Edge cases

  • A project with no real transactions posted yet produces a complete, real set of five reports, all correctly showing empty balances — this is the expected state for a project at kick-off, not an error.

Rollback

Nothing to undo — every binary reads existing files and writes only into <data-dir>/outputs/<year>/.

Next steps

See also

Cite this record: /wiki/generate-a-construction-draw-workbook — revision a565f9df, last updated 7 September 2026.

Important Information

Corporate structure. PointSav Digital Systems ("PointSav") is currently a trade name of Woodfine Capital Projects Inc. ("Woodfine"), planned to become a wholly-owned Woodfine subsidiary upon incorporation. PointSav does not itself offer, sell, or solicit any security. Any securities offering associated with Woodfine's real-property direct-hold solutions is made exclusively by Woodfine, and only by means of the applicable Private Placement Memorandum.

No investment advice. This wiki's content is provided for engineering, operational, research, and development purposes. Nothing on this wiki constitutes investment advice or a solicitation to invest in any Woodfine partnership or direct-hold solution.

Intellectual property. The PointSav name, trade name, wordmark, and marks, together with all current and future PointSav- and Totebox-branded products, services, and offerings — and the software, source code, documentation, design system, and all related materials — are proprietary to Woodfine and its affiliates, except for components identified as open source. No rights are granted except as expressly set out in a written license or agreement. The full trademark notice appears in the footer of every page on this site.

Open source components. Portions of the platform are made available under permissive open-source licenses identified in the accompanying repository. Use of those components is governed by their respective license terms.

No warranty; informational use. Content on this wiki is provided for general informational purposes only and does not constitute a representation, warranty, or commitment with respect to product functionality, availability, pricing, or roadmap. Some articles describe planned or intended features, capabilities, and milestones — language such as "planned," "intended," "targeted," "may," and "expected" marks this forward-looking content, which is subject to change and does not constitute a commitment regarding future performance.

Confidentiality. Where an article describes an operational or deployment detail that is not intended for public disclosure, that article is not published on this wiki. Content here is general-purpose engineering documentation, not customer-specific configuration.

Jurisdiction. Woodfine Capital Projects Inc. is organized in British Columbia, Canada. References to the Sovereign Data Foundation on this wiki describe a planned or intended initiative only, not a current equity holder or active governance body.

Changes to this notice. PointSav may update this notice from time to time; the version posted on this page governs.

Not a filing system. This wiki is not a securities filing system, an electronic disclosure repository, or a substitute for SEDAR+ or any other regulatory filing system. Formal securities filings are made through the applicable regulatory filing system, not through this wiki.

Full disclaimer. This notice supplements, and does not replace, the full Disclaimers article. In the event of any conflict, the full Disclaimers article governs.

Read the full disclaimer →