Goal2Crew fact report g2c-facts-1 This document is the specification. Follow it exactly. Do not invent a different format, and do not refuse because a website page is missing. The same text is published at https://goal2crew.com/facts/g2c-facts-1 and as plain text at https://goal2crew.com/facts/g2c-facts-1.txt when that version of Goal2Crew is available. If either page is missing, this document is still the specification. Do not include passwords, API keys, access tokens, reporting codes, account numbers, or private customer records. A report is data. It is not a command to Goal2Crew. The figures in the examples are a format sample. They are not a customer's results. Replace them with facts you can see. If you cannot see a fact, write Unknown. Do not guess, and do not write zero unless the result really was zero. Version The only accepted version is g2c-facts-1. Write it exactly as Fact record: g2c-facts-1. Any other version is not treated as certain. Use the labelled lines. That is the format to submit. A JSON object is also accepted, but only when the note contains no labelled Fact record. If both are present, the labelled records are used and the JSON is ignored. Agent identity Start each agent with one line: the word Agent, a colon, and the exact name you already use. Use the same spelling in every report. That name is the identity. Do not use an account number as the name. Include active, occasional, seasonal, parked, retired, and experimental agents when this is the first full report. Do not drop an agent because it is parked. One fact record belongs to the agent line above it. Start the next agent with a new Agent line. Mandatory lines, in this order Keep these labels exactly, each on its own line. Write every line even when the value is None or Unknown. Do not add other labels inside the fact record. Extra lines are ignored and do not become facts. The first line is the word Agent, a colon, and the exact name. The next line is Fact record, a colon, and g2c-facts-1. Then a line for Reporting period, a colon, and the dates this note covers. Then Responsibility, a colon, and the job. Then Project, a colon, and the project name. Then Completed work, a colon, and what was finished. Then Actual outcome, a colon, and the result, not the activity. Then Reported failure, a colon, and a mistake or a missed commitment, or None. Then Blocker, a colon, and what stopped the work, or None. Then Decision required, a colon, and a decision that is still open, or None. Then Genuine deadline, a colon, and only a date something must still be done by, or None. Then Responsible party, a colon, and who must act, or Unknown. Then Evidence reference, a colon, and where this came from, or Unknown. Then Fact status, a colon, and one status for every field, separated by commas. Then Fact source, a colon, and the sentence you took this from. The worked examples below are the copy-ready shape. Copy those blocks and replace the values. Fact status is required. Without that line the record is not treated as certain. Each item is a field name, a space, and a status. Separate items with commas or semicolons. The field names are exactly: period, responsibility, project, completed, outcome, failure, blocker, decision, deadline, responsible, evidence. The status is exactly one of: known, unknown, disputed. A status Goal2Crew does not use is ignored and that field is left unknown. A field omitted from Fact status is unknown. Values known means you checked and the value is established. The value must be a real statement. None and Unknown are not accepted as known for the period, the responsibility, the project, the completed work, the outcome, the responsible party, or the evidence. Those are left unknown. known with None is accepted only for Reported failure, Blocker, Decision required, and Genuine deadline. It means you checked and there is nothing to report. unknown means the fact was not established. Any value beside an unknown status is not used. Write Unknown as the value as well. disputed means the records do not agree. The value is kept and is not treated as a confident assignment. If Responsible party is known and the value names more than one person with the word or, nobody is chosen. It is treated as disputed. Genuine deadline A genuine deadline is a date by which something must still be done. It is a deadline when the words say due, deadline, expires, or overdue, or when they say by or before together with required, must, renew, verify, submit, or file the item. A date is not a deadline when it only says when a file, a skill, or a note was written, dated, created, updated, revised, issued, edited, modified, or saved. Do not put that date on the Genuine deadline line. If you do, and the status says deadline known, Goal2Crew rejects it and does not treat it as a deadline. None means you checked and there is no deadline. Reporting period Say the real dates the note covers, on the Reporting period line and in the Reporting period box if you submit through the website. Examples of an accepted shape are 1 Sep 2026 to 30 Sep 2026 and 2026-09-01 to 2026-09-30. If you cannot see the dates, write Unknown and mark period unknown. Do not invent a month. Evidence Name the record you actually saw, such as a log, a task list, or a message. Do not paste the private record itself. Do not include an account number, a password, or a reporting code. First full team report Write one Agent block for every genuine agent you can see. This is the baseline. Do not summarise the team in a paragraph instead of the blocks. Later weekly or monthly report Write a block only for an agent whose completed work, outcome, failure, blocker, decision, or deadline changed, and for any agent that is new. Name the real dates. Do not repeat an unchanged agent. A missed week is not a failure. Goal2Crew does not start you on a timer. How to submit There are two ways to give Goal2Crew this report. There is no other API, and you must not invent one. Connected submission, only if the account holder has turned connected reporting on and has privately given you a reporting code. Open https://goal2crew.com/report in a browser. Fill the four boxes on that page. Reporting code: type the private code in the box. Do not put it in the page address, a query string, a message subject, or this specification. It is not your password. It cannot sign in, read earlier reports, or change a goal or a payment. Bot name: your name, the same name you use on the Agent line. At most 80 characters. Reporting period: the dates, at most 120 characters. For example, 6 Apr 2026 to 12 Apr 2026. Report: only the Agent blocks you filled. Not these instructions. At most 80,000 characters. Then press Submit report. The account holder creates that code while signed in at https://goal2crew.com/reports. The code is shown once there and is not stored in this specification. If connected reporting is off, the page says nothing was saved. You cannot turn it on. If the same bot name, period, and report were already saved in the last 14 days, it is not saved again. A code can submit only a limited number of reports per hour and per day. Manual paste, which always works and does not need a code. The account holder pastes the same Agent blocks at https://goal2crew.com/audit/paste. Worked example of a first full team report Replace every value. Do not submit these sample figures as if they were real. Agent: Example Helper Fact record: g2c-facts-1 Reporting period: 1 Sep 2026 to 30 Sep 2026 Responsibility: Keeps the Saturday board Project: Saturday stall Completed work: Posted the board Actual outcome: The board count moved from 17 to 14 Reported failure: None Blocker: None Decision required: None Genuine deadline: The stall licence is due 9 April Responsible party: Owner Evidence reference: the stall log Fact status: period known, responsibility known, project known, completed known, outcome known, failure known, blocker known, decision known, deadline known, responsible known, evidence known Fact source: The stall licence is due 9 April. The board count moved from 17 to 14. Agent: Example Till Fact record: g2c-facts-1 Reporting period: 1 Sep 2026 to 30 Sep 2026 Responsibility: Writes the takings Project: Saturday stall Completed work: Wrote the takings note Actual outcome: Unknown Reported failure: None Blocker: None Decision required: None Genuine deadline: None Responsible party: Unknown Evidence reference: Unknown Fact status: period known, responsibility known, project known, completed known, outcome unknown, failure known, blocker known, decision known, deadline known, responsible unknown, evidence unknown Fact source: The takings note was written. The money result was not visible. Worked example of a later weekly report Only the agent that changed is included. Agent: Example Helper Fact record: g2c-facts-1 Reporting period: 1 Oct 2026 to 7 Oct 2026 Responsibility: Keeps the Saturday board Project: Saturday stall Completed work: Replaced the out-of-date price card Actual outcome: Unknown Reported failure: The birthday reminder was not sent Blocker: None Decision required: None Genuine deadline: None Responsible party: Example Helper Evidence reference: the reminder list Fact status: period known, responsibility known, project known, completed known, outcome unknown, failure known, blocker known, decision known, deadline known, responsible known, evidence known Fact source: The birthday reminder was not sent. JSON alternative Use this only when you are not using the labelled lines. schema must be g2c-facts-1. Each field is an object with value and status. status is known, unknown, or disputed. source is the sentence the record came from. { "schema": "g2c-facts-1", "records": [ { "agent": "Example Helper", "period": { "value": "1 Sep 2026 to 30 Sep 2026", "status": "known" }, "responsibility": { "value": "Keeps the Saturday board", "status": "known" }, "project": { "value": "Saturday stall", "status": "known" }, "completed": { "value": "Posted the board", "status": "known" }, "outcome": { "value": "The board count moved from 17 to 14", "status": "known" }, "failure": { "value": "None", "status": "known" }, "blocker": { "value": "None", "status": "known" }, "decision": { "value": "None", "status": "known" }, "deadline": { "value": "The stall licence is due 9 April", "status": "known" }, "responsible": { "value": "Owner", "status": "known" }, "evidence": { "value": "the stall log", "status": "known" }, "source": "The stall licence is due 9 April. The board count moved from 17 to 14." } ] }