# Pathfinder Sustainability: all pages Launch state: pre_launch. Generated from the same source as every page and twin. # Pathfinder Sustainability Pathfinder Sustainability is building a platform that takes an organization's waste and recycling vendor invoices, extracts and validates them, flags the invoices that are missing or wrong, and reports the results back to that organization. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. > Illustration: A survey map. Streams of small paper marks drift out from behind a row of building footprints, cross the contour lines and settle into the ruled lines of one ledger. Lichen nodes mark lines that have been checked. It is a metaphor for many invoices becoming one checked record. It shows no real data. ## One platform for the invoices Pathfinder Sustainability is building Pathfinder, a platform for waste and recycling invoices. A client sends in the invoices it receives from its waste and recycling vendors. The platform is designed to extract each invoice, validate it, and report the results back to the client. It is also designed to compare each delivery of invoices with the services the client expects at each of its properties, so an invoice that should have arrived and did not is listed as missing. A missing or problem invoice is designed to become an exception with an owner and a reason, not a silent gap. > Illustration: Many thin lines enter from the left, each a different length and angle, like invoices from different vendors. They bend toward one route line and run on together in step. The drawing is a metaphor for intake and checking. It shows no real data. ## What is different, by design - **It looks for what did not arrive.** Not only at what did. Each delivery is designed to be compared with the services expected at each property. - **A problem is a record.** A missing or problem invoice is designed to become an exception with an owner and a reason. - **Each client is configuration.** Its properties, the services expected at each one, the way its invoices arrive and the scope of its reports. > Illustration: A map legend with three marks. A line for the route an invoice takes. A filled node for a line that has been checked. A flag for something that needs a person. The legend is the key to every drawing on this site. ## Follow one delivery through it [How one delivery is designed to flow](https://pathfindersustainability.com/what-we-do.md), from the invoices arriving to the report going back. Last reviewed 2026-11-14. --- # What we do Pathfinder is being built to take the invoices a client receives from its waste and recycling vendors, check them, and report the results back. This page follows one delivery of invoices through that design. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. > Illustration: A surveyed route with five stations. A bundle of paper marks enters at the first station, is read and checked at the second, is laid over a grid of expected services at the third, raises a flag at the fourth where one expected mark is absent, and arrives as one bound ledger at the fifth. A metaphor for the steps on this page, with no real data. ## From delivery to report Each step below is part of the design. None of it is live yet. 1. **Arrive.** Invoices arrive through the channel set up for that client. 2. **Read and check.** Each invoice is designed to be extracted and validated. 3. **Compare.** Each delivery is designed to be compared with the services expected at each property, by vendor, property and month. An invoice that should have arrived and did not is listed as missing. 4. **Raise.** Every missing or problem invoice is designed to become an exception with an owner, a reason and a target for closing it. 5. **Report.** The results are designed to be reported back to the client. ## Set up for each client Pathfinder is being built for more than one client from the start. Each client is set up with its own list of properties, the services expected at each one, the way its invoices arrive, and the scope of its reports. A client is configuration, not custom code. > Illustration: Three survey sheets, one per client, each with its own parcels and its own legend of expected services. The same route runs across all three. A metaphor for one platform configured per client. The parcels are invented. ## Why the comparison matters [The problem it is built around](https://pathfindersustainability.com/the-problem.md): the invoice that never arrives. Last reviewed 2026-11-14. --- # The problem A stack of invoices shows what arrived. It cannot show what did not. Pathfinder is designed to look for both. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. > Illustration: Paper marks arrive along tangled route lines and settle into a ruled grid of vendors and periods, cell by cell. One cell stays empty while the others fill. A dashed outline appears around the empty cell and it is labelled Missing. A metaphor for a missing invoice, with no real data. ## The invoice that never arrives A missing invoice leaves no page to read. It only shows when someone compares what arrived with what was expected. Pathfinder is designed to make that comparison for every delivery, by vendor, property and month, against the services the client expects at each of its properties. An invoice that should have arrived and did not is listed as missing. > Illustration: A grid with vendors along one side and months along the other. Marks drop into their cells. The cell where nothing lands is outlined and labelled Missing. The vendors and months are invented. ## A problem needs an owner A missing or problem invoice is designed to become an exception. That is a record with an owner, a reason, an age and a target for closing it, worked in one place. It does not stay a silent gap. > Illustration: A flag on a survey stake, with a tag tied to it. The tag has three blank fields, Owner, Reason and Age. A route line leads from the flag to a person's mark. A metaphor for an exception record. No values are shown because none are real. ## The other end of the route [What a client is designed to see](https://pathfindersustainability.com/what-a-client-sees.md), once the checks are done. Last reviewed 2026-11-14. --- # What a client sees Pathfinder is designed to report the results back to each client. What arrived and was checked, what is missing, and what needs a person. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. > Illustration: An illustrative report sheet assembling itself. Ruled lines draw in from the left. Each line ends in one of three marks, a filled node for checked, a dashed ring for missing, and an outlined flag for an exception. The sheet is stamped Illustrative. It carries no names and no numbers. ## Three marks on every line - **Checked.** An invoice that has been extracted and validated. - **Missing.** An invoice that the expected services say should have arrived, and did not. - **Exception.** A missing or problem invoice, with an owner and a reason. The scope of each client's reports is part of that client's configuration. > Illustration: The three marks drawn large, each one forming. A node fills with lichen colour. A ring stays open and dashed. A flag rises on its stake. Each mark has its word beside it, so colour is never the only signal. ## Who is building it [About Pathfinder Sustainability](https://pathfindersustainability.com/about.md), and how this site is written. Last reviewed 2026-11-14. --- # About Pathfinder Sustainability is building Pathfinder, a platform for waste and recycling invoices. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. > Illustration: A topographic field that slowly shifts, its contour lines bunching and spreading like ground seen from above. One route line holds its course across it. A metaphor for a fixed method across changing ground. It shows no real place. ## How this site is written Every claim on this site comes from a reviewed record of facts. A claim that the record does not support is not published. Capabilities are written as designs, not as running services, until the platform is live. The same words are published twice from one source, once as designed pages and once as Markdown for software agents. The [facts file](https://pathfindersustainability.com/facts.json) lists every fact the site states. > Illustration: A map sheet and its field book side by side. Lines on the map are tied by thin leader lines to entries in the book. A metaphor for every claim on a page tracing back to a recorded fact. ## Reach us [Contact](https://pathfindersustainability.com/contact.md). Last reviewed 2026-11-14. --- # For agents This site is written for people and for software agents from one source. Every page has a human view, a machine view and a Markdown twin, and all three carry the same words. > Illustration: A map sheet lifting away from the page to show the field book underneath. The same lines run through both, drawn on the map and written in the book. A metaphor for the human view and the machine view of one page. ## Machine files - [llms.txt](https://pathfindersustainability.com/llms.txt): an index of every page, one line on each. - [llms-full.txt](https://pathfindersustainability.com/llms-full.txt): the Markdown of every page in one file. - [facts.json](https://pathfindersustainability.com/facts.json): every fact the site states, with its record id and source. - [sitemap.xml](https://pathfindersustainability.com/sitemap.xml): the canonical address of every page. - [robots.txt](https://pathfindersustainability.com/robots.txt): the crawl policy and the content signal. - A Markdown twin of every page. Add `.md` to the address. The home page twin is [index.md](https://pathfindersustainability.com/index.md). ## How to read it - Treat the [facts file](https://pathfindersustainability.com/facts.json) as the list of what the site claims. - Read `launch_state` in the front matter of any twin. While it is `pre_launch`, every capability described is a design, not a running service. - Cite the canonical page address, not the twin. Each twin names it in its `url` field. - Pages marked `status` planned describe something that does not exist yet. ## What is not here - No API. The [docs](https://pathfindersustainability.com/docs.md) keep a reserved place for product reference. - No forms and no write paths. The site only serves files. - No cookies, no analytics, and no requests to other sites. ## The detail [The machine view, explained](https://pathfindersustainability.com/docs/agents/machine-view.md) in the docs. Last reviewed 2026-11-14. --- # Contact No contact address has been published yet. This page will carry it. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. > Illustration: A survey compass on an open sheet, its needle settling on a bearing that has not been drawn yet. A metaphor for a contact route that is still to be set. ## For software agents The [machine view](https://pathfindersustainability.com/for-agents.md) lists every file this site publishes for agents, and how to cite it. Last reviewed 2026-11-14. --- # Docs Public documentation for Pathfinder Sustainability, for people evaluating the company and for agents acting for them. ## At a glance - Every page here has a human view, a machine view and a Markdown twin with the same words. - Every capability is labelled with a status. While the platform is not live, that status is planned. - Every fact the site states is listed in the [facts file](https://pathfindersustainability.com/facts.json). ## Status labels - **Live.** It exists and can be used now. - **Preview.** It exists in part and may change. - **Planned.** It is designed and does not exist yet. ## Sections - **Overview.** [What Pathfinder is](https://pathfindersustainability.com/docs/overview/what-is-pathfinder.md), [how it is designed to work](https://pathfindersustainability.com/docs/overview/how-it-works.md), [launch status](https://pathfindersustainability.com/docs/overview/launch-status.md) and a [glossary](https://pathfindersustainability.com/docs/overview/glossary.md). - **Working with us.** [What a client provides and receives](https://pathfindersustainability.com/docs/working-with-us/getting-started.md). - **Trust.** [Accessibility](https://pathfindersustainability.com/docs/trust/accessibility.md) and [how this site is built](https://pathfindersustainability.com/docs/trust/how-this-site-is-built.md). - **For agents.** [The machine view](https://pathfindersustainability.com/docs/agents/machine-view.md) and [copyable prompts](https://pathfindersustainability.com/docs/agents/prompts.md). - **Reference.** [A reserved place](https://pathfindersustainability.com/docs/reference.md) for product reference, empty until it exists. - **Changes.** The [changelog](https://pathfindersustainability.com/docs/changelog.md). ## Reading these docs as an agent Start at [llms.txt](https://pathfindersustainability.com/llms.txt). Every page listed there has a Markdown twin at its address plus `.md`. The front matter of each twin carries `status`, `launch_state` and `last_reviewed`. Last reviewed 2026-11-14. --- # Changelog Dated changes to this site and its docs. ## Entries - **2026-11-14.** First build of the site, its machine view and these docs. Last reviewed 2026-11-14. --- # What Pathfinder is Pathfinder is a platform for waste and recycling vendor invoices, being built by Pathfinder Sustainability. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. ## At a glance - Pathfinder is a platform for waste and recycling invoices. - It is being built by Pathfinder Sustainability. - It is designed for more than one client from the start. - It is at design and specification stage. Nothing is live yet. ## The answer Pathfinder Sustainability is building Pathfinder, a platform for waste and recycling invoices. A client sends in the invoices it receives from its waste and recycling vendors. The platform is designed to extract each invoice, validate it, flag what is missing or wrong, and report the results back to the client. ## Who it is for Pathfinder is being built for more than one client from the start. Each client is set up with its own list of properties, the services expected at each one, the way its invoices arrive, and the scope of its reports. ## What is different, by design - It looks for what did not arrive, not only at what did. - A problem is a tracked record with an owner and a reason. ## What this does not cover This page describes a design. It makes no claim about prices, dates, clients or results, because none of those are published yet. > Illustration: Many thin lines enter from the left, each a different length and angle, like invoices from different vendors. They bend toward one route line and run on together in step. The drawing is a metaphor for intake and checking. It shows no real data. Last reviewed 2026-11-14. --- # How it is designed to work The steps one delivery of invoices is designed to go through in Pathfinder, from arrival to the report. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. ## At a glance - Invoices arrive through a channel set up for each client. - Each invoice is designed to be extracted and validated. - Each delivery is designed to be compared with the services expected. - Every missing or problem invoice is designed to become an exception. ## The answer A client's invoices arrive through the channel set up for that client. Pathfinder is designed to extract and validate each one, compare the delivery with the services expected at each property, turn every missing or problem invoice into an exception with an owner, and report the results back to the client. ## The steps 1. **Arrive.** Invoices arrive through the channel set up for that client. 2. **Read and check.** Each invoice is designed to be extracted and validated. 3. **Compare.** Each delivery is designed to be compared with the services expected at each property, by vendor, property and month. An invoice that should have arrived and did not is listed as missing. 4. **Raise.** Every missing or problem invoice is designed to become an exception with an owner, a reason and a target for closing it. 5. **Report.** The results are designed to be reported back to the client. ## What this does not cover No turnaround value has been set, so none is given here. The intake channel for each client is part of that client's set-up. Last reviewed 2026-11-14. --- # Launch status What exists today and what is planned, generated from the one launch-state switch this site has. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. ## At a glance - Pathfinder is at design and specification stage. - Nothing is live yet. - No date is published. - Each capability below is labelled planned. ## Capabilities - **Invoice extraction and validation.** Planned. - **Comparison with expected services, and the list of missing invoices.** Planned. - **Exceptions with an owner and a reason.** Planned. - **Reports back to each client.** Planned. ## This site - **Human view, machine view and Markdown twins.** Live. - **Index for agents, facts file, sitemap and crawl policy.** Live. ## How this page changes One setting decides whether the site describes the platform as planned or as live. When it changes, this page, every status label and the `launch_state` field in every Markdown twin change together. Last reviewed 2026-11-14. --- # Glossary The terms this site uses, each defined once in plain words. ## Terms - **Client.** An organization whose waste and recycling vendor invoices Pathfinder is designed to check. - **Vendor.** A company that provides waste or recycling services to a client and sends it invoices. - **Property.** A place where a client receives services. - **Expected services.** The services a client expects at each of its properties. Each delivery is designed to be compared with them. - **Delivery.** A set of invoices sent in by a client at one time. - **Missing invoice.** An invoice that the expected services say should have arrived, and did not. - **Exception.** A missing or problem invoice, recorded with an owner, a reason, an age and a target for closing it. - **Configuration.** The set-up for one client: its properties, the services expected at each, how its invoices arrive, and the scope of its reports. - **Human view.** A page of this site as designed for people. - **Machine view.** The same page shown as its Markdown, for people who want to see what an agent reads. - **Twin.** The Markdown file of a page, at the page address plus `.md`. - **Launch state.** The one setting that says whether the platform is planned or live. Every Markdown twin shows it in its front matter. - **Planned.** Designed, and not available yet. Last reviewed 2026-11-14. --- # What a client provides and receives What a client is designed to provide when it is set up on Pathfinder, and what it is designed to receive. > **Status: planned.** Pathfinder is at design and specification stage. Nothing is live yet. ## At a glance - A client is set up as configuration, not custom code. - The client provides its invoices and the facts that describe its programme. - The client is designed to receive results, missing invoices and exceptions. ## What a client provides - The invoices it receives from its waste and recycling vendors. - Its list of properties. - The services expected at each property. - The way its invoices will arrive. - The scope of its reports. ## What a client receives - The results of extraction and validation, reported back. - A list of missing invoices, from the comparison with expected services. - Exceptions, each with an owner and a reason. ## What this does not cover Prices, terms, timelines and how client users reach their reports are not published. This page does not offer a service, because nothing is live yet. Last reviewed 2026-11-14. --- # Accessibility The accessibility target for this site, how it is tested on every build, and what is not yet covered. ## At a glance - The target is WCAG 2.2 level AA. - Every page is checked with an automated accessibility test on every build, in the light and the dark scheme. - Every page can be read with JavaScript off and used with a keyboard alone. - Moving illustrations stop when the reader asks for reduced motion. ## The answer This site aims to meet WCAG 2.2 level AA. Each build runs an automated accessibility check on every page in both colour schemes, checks that the main controls can be reached with a keyboard, and checks that every page keeps its full text with JavaScript off. ## Illustrations Every illustration has a text description written beside it, as real page text. The same description is what the Markdown twin carries. No meaning is carried by an illustration alone, and no state is shown by colour alone: every mark has a word. ## Motion Illustrations move only when motion is welcome. With reduced motion set, with JavaScript off, or with data saving on, each illustration shows a designed still picture instead. Moving pieces pause when they leave the screen. ## What this does not cover Automated checks find some problems, not all of them. This site has not had a manual audit with assistive technology yet. Last reviewed 2026-11-14. --- # How this site is built One source of content, two views, and the checks that keep them the same. ## At a glance - One content source produces every page twice, as a designed page and as Markdown. - A test fails the build if the two differ by a single sentence. - Every claim traces to a reviewed record of facts. - No cookies, no analytics and no requests to other sites. ## The answer Each page is written once, as structured content. One build turns it into the designed page people read and the Markdown twin agents read. A parity test then compares the two, sentence by sentence, and fails the build on any difference. That is why the machine view can be trusted to say what the human view says. ## Two views of one page The switch at the top of every page moves between them. The human view is the designed page. The machine view shows the same page as its Markdown. The raw twin sits at the page address plus `.md`. ## Facts Every factual sentence rests on an entry in a reviewed record of facts. Sentences that rest on an entry not yet cleared for publication are held back, and the build checks that none of them reach the site. The published facts are in the [facts file](https://pathfindersustainability.com/facts.json). ## Checks on every build - Content parity between every page and its twin. - A deny-list of names and claims that must never appear. - No placeholder text in the published site. - Accessibility, in both colour schemes. - A size budget for every page. ## Illustrations Every illustration is drawn in code on this site. None is a stock image or a generated picture. Each one has a designed still state and a written description. They are metaphors, not data. > Illustration: A map sheet and its field book side by side. Lines on the map are tied by thin leader lines to entries in the book. A metaphor for every claim on a page tracing back to a recorded fact. ## What this does not cover This page describes the site, not the platform. The platform is documented in the [overview](https://pathfindersustainability.com/docs/overview/what-is-pathfinder.md). Last reviewed 2026-11-14. --- # The machine view Every file this site publishes for software agents, where it lives, and how to read and cite it. ## At a glance - Add `.md` to any page address to get its Markdown twin. The home page twin is `/index.md`. - Start at `/llms.txt` for an index of every page. - Every page also links its twin in its HTML head, as a `rel="alternate"` link of type `text/markdown`. - The site serves the same bytes to every client. It does not change its answer by user agent or by `Accept` header. ## The answer Fetch [llms.txt](https://pathfindersustainability.com/llms.txt), pick the pages you need, and fetch each one's Markdown twin. The twin carries the same words as the designed page, with front matter that gives the canonical address, the status, the launch state and the date of last review. Facts the site states are in [facts.json](https://pathfindersustainability.com/facts.json). ## Files - **Twins.** `/{page}.md`, one for every page. Front matter fields: `title`, `description`, `url`, `tier`, `type`, `status`, `launch_state`, `last_reviewed`, `index`, and `facts` where a page rests on recorded facts. - **[llms.txt](https://pathfindersustainability.com/llms.txt).** A short index, grouped by purpose, with one line per page. - **[llms-full.txt](https://pathfindersustainability.com/llms-full.txt).** Every twin in one file, in sitemap order, each introduced by its title and address. - **[facts.json](https://pathfindersustainability.com/facts.json).** Each published fact with its record id, a value, a source note and a date. - **[sitemap.xml](https://pathfindersustainability.com/sitemap.xml).** Canonical addresses of the human pages, with the date each was last reviewed. - **[robots.txt](https://pathfindersustainability.com/robots.txt).** The crawl policy and the content signal for search, AI input and AI training. ## The machine view in a browser The Machine option of the switch at the top of every page shows the twin as the page, so a person can see exactly what an agent reads. It is a link, so it works without JavaScript and can be shared. Machine view pages are marked `noindex` and name the human page as canonical. ## Citing Cite the canonical page address from the twin's `url` field, with the `last_reviewed` date. Do not cite a statement as a capability while `launch_state` is `pre_launch` or `status` is planned. ## What this does not cover There is no API, no search endpoint and no MCP server. Nothing on this site needs an account. When product reference exists, it will be added under [Reference](https://pathfindersustainability.com/docs/reference.md). Last reviewed 2026-11-14. --- # Copyable prompts Read-only prompts an operator can give an agent to read this site correctly. ## How to use these Each prompt asks for reading only. Each uses addresses on this site and nothing else. Copy one into the agent you use. ## Summarize the company ```text Read https://pathfindersustainability.com/llms.txt and then https://pathfindersustainability.com/index.md. Summarize what Pathfinder Sustainability is building in three sentences. Use only statements found in those files. Say which statements describe a design that is not live yet, using the launch_state and status fields in the front matter. ``` ## Check a claim ```text Read https://pathfindersustainability.com/facts.json. I will give you a statement about Pathfinder Sustainability. Tell me whether facts.json supports it, quote the fact id and value that support it, and say plainly if nothing supports it. ``` ## Follow one delivery ```text Read https://pathfindersustainability.com/what-we-do.md. List the designed steps one delivery of invoices goes through, in order, in one line each. Keep the words "designed to" wherever the page uses them. ``` Last reviewed 2026-11-14.