# Task: Check a project’s key evidence Trace conclusions through entities, assets, funding and rights. ## Prepare Prepare authorized entity, asset, contract, funding and rights documents, with dates, versions and missing items. ## Produce Produce a four-chain map, evidence register, conflicts and gaps, and conditional next steps. ## Check Trace important conclusions to specific documents. Distinguish intention, signing, transfer and operation; do not present unverified items as completed. ## Conditions Check documents and relationships before judging next-step conditions. The platform playbook illustrates phased acceptance only; it does not establish project assets, transactions or rights. Confirm inputs, conditions, sources and versions. List missing information; do not invent it. Identify goals, budgets, rights, permissions and final decisions that require human confirmation. ## Original text and version - Thinking: How Can Industry Operations and Capital Arrangements Support Each Other? | V1.0 | https://yutengfei.com/en/journal/industry-operations-capital-alignment/ Markdown: https://yutengfei.com/en/journal/resources/industry-operations-capital-alignment.md Identify how industry operations and capital arrangements need to support each other. - Methods: Four questions I check first when reviewing project materials | V1.0 | https://yutengfei.com/en/journal/project-material-review/ Markdown: https://yutengfei.com/en/journal/resources/project-material-review.md Check project documents for entities, facts, relationships and gaps. - Models: Understanding a Project Through Four Chains: Entities, Assets, Funds and Rights | V1.0 | https://yutengfei.com/en/journal/project-four-chains/ Markdown: https://yutengfei.com/en/journal/resources/project-four-chains.md Map entities, assets, funding and rights into traceable relationships. - Playbooks: Building an Industry Digital Platform in Verifiable Stages | V1.0 | https://yutengfei.com/en/journal/phased-industry-digital-platform/ Markdown: https://yutengfei.com/en/journal/resources/phased-industry-digital-platform.md Consult the phased acceptance approach to distinguish plans from completed work. - Tools: Project evidence ledger: trace every conclusion to its sources | V1.0 | https://yutengfei.com/en/journal/project-evidence-ledger/ Markdown: https://yutengfei.com/en/journal/resources/project-evidence-ledger.md Register evidence, locations, conflicts and follow-up for important claims. - Training: Draw the Project: A Four-Chain Evidence Exercise | V1.0 | https://yutengfei.com/en/journal/project-four-chain-exercise/ Markdown: https://yutengfei.com/en/journal/resources/project-four-chain-exercise.md Rehearse the four chains with a fictional project and check for confused statuses. ## Associated Skill The public Skill page provides an overview. Its full execution files are in a private repository and require access. OTCQB Project Collaboration: https://yutengfei.com/en/skills/otcqb-project-workflow/ ## Record results, deviations and knowledge or steps that need revision. Version: V1.0 · 2026-11-05 https://yutengfei.com/en/journal/pathways/project-evidence/ --- Select resources and sections as needed instead of indiscriminately loading every document. Exports retain existing licenses and third-party notices. Downloading grants no additional adaptation, commercial-use or training rights. --- # How Can Industry Operations and Capital Arrangements Support Each Other? - Author: Andrew David W.Y. - Source: https://yutengfei.com/en/journal/industry-operations-capital-alignment/ - Version: V1.0 - Published: 2026-10-19 - Revised: 2026-10-19 - Content status: Full text published - Content type: Thinking (ideas) - Research topics: Stakeholder Capital Governance (stakeholder-governance) - Ecosystem perspectives: Resource Ecosystem (resource) · Operations & Management Ecosystem (operations) · Capital Ecosystem (capital) ## Use this resource **Purpose**: A business can face a familiar sequence as it grows: customers want the product, but delivery capacity falls behind; the team wants more capacity, but funding is not arranged; the money finally arrives, but the operating plan has changed. **Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify. **Thinking · Premises and reasoning** **Evidence and validation limits**: The example illustrates how to analyze the situation and use the approach. When applying it, substitute actual business records for the example conditions and check the judgment and outcome. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text. This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output. ## Full article A business can face a familiar sequence as it grows: customers want the product, but delivery capacity falls behind; the team wants more capacity, but funding is not arranged; the money finally arrives, but the operating plan has changed. Operations and capital continually affect each other. In discussion, however, they are often treated separately. Operating teams focus on products, orders and delivery. Capital discussions focus on financing, valuation and exit. Each has its own logic. Within one project, the two need to connect. I would start with a specific question: **which operating capability is this capital arrangement meant to improve?** Then ask what resources are needed, when they should be committed, what costs and responsibilities follow, and how the effect will be checked. The reverse question matters too: do the operating results support the original capital arrangement? If circumstances change, what should happen next? I understand the relationship in both directions: **operations provide a basis for resource allocation, capital arrangements support implementation, and results inform the next decision.** ## 1\. Identify the operating constraint first Saying a company needs money leaves important questions unanswered. Which part of the funding is missing, and what problem is it meant to solve? Is the business buying materials to deliver existing orders, or developing a new capability? Have payment cycles lengthened, or has the product not yet won customer acceptance? Is equipment lacking, or is existing equipment underused? These situations may call for very different responses. Some need additional investment. Others first need changes to processes, customer terms or the product. Some projects have a sound basis but lack resources. Others still need to test demand and costs. If the problem has not been identified, rapid financing may fund an untested direction. What began as a small experiment can become a large commitment that is difficult to reverse. I would describe the operating problem in one concrete sentence: what capability is missing, what result is affected and what action is proposed to improve it. “Grow the business” is too broad. “Existing orders take too long to deliver; equipment modifications and staff training are proposed to improve delivery” gives us something to examine. Will those modifications address the constraint? Is customer demand continuing? Are the materials, people and supporting conditions available too? **A clear operating gap gives the capital discussion a defined purpose.** ## 2\. Examine the money and its conditions together Once the operating need is clear, identify the resource gap: how much is needed, when, where it may come from and on what terms. A capital arrangement involves more than receiving money. It also brings a term of use, a cost, rights, governance responsibilities and continuing obligations. Each condition enters the operating process. Repayable funding needs a repayment schedule considered alongside operating cash receipts. Arrangements changing equity need clear rights, responsibilities and expectations for continuing cooperation. An industry partner's proposed resources and coordination also need checking against what that partner can actually provide. If capability takes time to build while the funding requires rapid recovery, the timetable may create pressure. Conversely, a short-term working-capital need warrants consideration before committing to rights arrangements with much longer effects. I would discuss the following in one table. | What operations must explain | What the capital arrangement must address | | --- | --- | | Which capability is to improve | The specific uses of money and other resources | | How long it takes for input to produce results | The fit between funding term, payments and recovery | | Which conditions are established and which need testing | The initial commitment and evidence needed for further commitments | | What happens if results fall short | Responsibilities, deviations and existing obligations | | How the effect of the input will be assessed | The records, measures and review procedures | The table does not select the best financing method. It allows operating needs and capital terms to be checked against one another. ## 3\. Trace the input through to operating results The contribution of capital to an industry needs to be assessed through specific changes. Did equipment improve delivery capacity? Did a new system shorten reconciliation time? Did a partner make supply and service more stable? Did additional sales spending lead customers to keep buying? These questions need actual records. Money entering the enterprise means a resource has arrived. Using it as planned is implementation. Changes in products, delivery, quality and cash collection begin to show operating results. Keeping those levels separate makes it easier to locate a problem. Construction may finish on time while customer use and payment lag. Sales may rise along with receivables, leaving considerable cash pressure. Higher capacity may also require more procurement, inventory and staffing, changing the original funding estimate. Results therefore cannot be assessed through one growth figure alone. Accounting provides a useful distinction: IAS 7 separates cash flows into operating, investing and financing activities. Cash obtained through financing and cash generated by ordinary operations need separate observation. [IFRS Foundation: IAS 7](https://www.ifrs.org/issued-standards/list-of-standards/ias-7-statement-of-cash-flows.html/) An operating team also needs the next connections: what the money funded, which capability formed, what revenue and expenditure followed, how much cash was collected and what obligations remain. **To assess whether a capital arrangement helped, trace it back through use of funds, implementation and operating results.** ![Figure 1: Operations and capital align through one implementation plan and operating evidence](https://yutengfei.com/journal/industry-operations-capital-alignment/materials/en/asset-01.svg) _Figure 1 shows two workstreams that need to be checked against each other. Operating evidence informs the next assessment; further resource allocation still depends on actual conditions._ [Download Figure 1 as SVG](https://yutengfei.com/journal/industry-operations-capital-alignment/materials/en/asset-01.svg) ## 4\. How operating results support the next capital assessment Operations can provide both cash and verifiable evidence for the next capital discussion. Customer demand, delivery records, cost changes, actual collections and the stability of cooperation help explain whether an earlier judgment held, what further investment would address and what remains uncertain. Separate two relationships here. The first is **resources**. After relevant costs, obligations, operating needs and authorization requirements have been addressed, the available part of operating cash may be considered for further investment. The amount and use still need separate confirmation. The second is **evidence**. Clearer operating records give the enterprise and potential partners a more concrete basis for discussing the next stage: which capabilities exist, which inputs remain under testing and what needs adjustment. Better evidence can improve discussion and judgment. It does not decide whether another party will invest, nor guarantee financing, a higher valuation or an exit opportunity. Market conditions, transaction terms, governance and each party's risk assessment all affect the outcome. I therefore see the next capital arrangement as a new assessment. Earlier experience can help, while earlier conclusions must face new facts. ## 5\. Bring governance into the project with the investment Connecting operations and capital also requires clarity about who may decide the next step. Who proposes the use of funds, checks the budget, approves it, implements the commitment and reports changes? If the plan changes, who confirms the adjustment, and which changes require agreement from others? These arrangements affect whether the project can proceed on its original terms. Unclear sources, uses, rights and obligations make consistent operating decisions difficult. Without implementation records, resource providers also have little basis for deciding how to continue cooperating. The OECD governance principles connect oversight of strategy, budgets, major capital expenditure, operating performance and risk. A useful lesson is to consider resource commitments alongside continuing oversight. The responsible organizational level still depends on the actual structure and applicable arrangements. [G20/OECD Principles: Responsibilities of the Board](https://www.oecd.org/en/publications/g20-oecd-principles-of-corporate-governance-2023_ed750b30-en/full-report/component-8.html) In practice, I suggest retaining four connections: - Each major input has a defined operating task. - Each implementation stage has a responsible person and verifiable results. - Each resource arrangement has corresponding rights, obligations and conditions of use. - Each important adjustment has a decision basis, appropriate authority and an update record. These connections help capital continue supporting operations and allow operating changes to reach decision-makers promptly. ## 6\. Connect the two through a hypothetical scenario This scenario was written to explain the relationships. It does not describe a real enterprise or project. Suppose a manufacturer has long delivery times for existing orders. Its team proposes modifying equipment to improve delivery capacity and prepares an additional funding arrangement. “Expand capacity and revenue” is not enough to explain why the investment is needed or how it will be implemented. I would break it into steps. First, examine orders, equipment use and delivery records to establish whether equipment is the main constraint. Then check the modification plan, staff training, material supply and customer acceptance conditions. Estimate the time from commitment to actual cash collection. Use that timetable and those implementation conditions to discuss the use of funds, available funding term, cost and each party's responsibilities. Establish checkpoints for modification, trial operation, customer delivery and cash collection. If trial operation meets the agreed targets and the customer completes the relevant acceptance process, assess the next investment stage under the effective arrangements. If the equipment is improved but order demand changes, reassess the scope of expansion. Existing contractual obligations remain subject to their arrangements. Whether to make further commitments is a separate decision. If delivery improves but cash collection is delayed, investigate payment terms, acceptance disputes and the customer's circumstances. Increased output alone cannot establish that the whole project has achieved its objectives. In this example, operations define a problem, capital arrangements help secure resources, governance and records connect implementation, and actual results inform the next assessment. Working through the relationship brings discussion to the points where judgment is needed. ![Figure 2: Implementation, stage reviews and decisions to continue, adjust or pause additional investment](https://yutengfei.com/journal/industry-operations-capital-alignment/materials/en/asset-02.svg) _Figure 2 is a framework for implementation discussions. Pausing or adjusting additional investment requires the appropriate authority and effective agreements. It does not automatically suspend existing payments or other obligations._ [Download Figure 2 as SVG](https://yutengfei.com/journal/industry-operations-capital-alignment/materials/en/asset-02.svg) ## 7\. Reassess when conditions change Changing conditions are not unusual. What matters is whether the change reaches the assessment in time. I suggest reviewing three questions separately. **Does the operating reason still hold?** What has changed in demand, costs, delivery and collections? Has the original constraint improved, or has a new one emerged? **Can the resource conditions still support the arrangement?** Do available funds, restrictions, terms, supporting inputs and obligations still fit the operating plan? **How should the next decision be confirmed?** What evidence and approval are needed to continue, adjust or pause additional investment? What needs renegotiation with partners, and how will existing obligations be handled? Clear answers support both continuation and adjustment. When results deviate, reducing the scope or changing the sequence can also be a responsible operating and resource decision. ## Keep the connections open to review Mutual support between operations and capital depends on connections that can be checked. Operations should explain the problem the resources are intended to solve. Capital arrangements should explain the conditions and responsibilities involved. After implementation, actual results should test the original judgment. I want an enterprise to become increasingly clear about why it is investing, what the input improved and what will inform its next decision. Continually answering those questions gives the relationship between industry and capital a firmer basis. ## Related reading - [Understanding a funding model: from rules to realized proceeds](https://yutengfei.com/en/journal/capital-rules-and-mechanism-diagnosis/) - [How to put funding sources and uses in one table](https://yutengfei.com/en/journal/funding-sources-uses-table/) [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training. [AI usage guide](https://yutengfei.com/en/journal/ai/) --- # Four questions I check first when reviewing project materials - Author: Andrew David W.Y. - Source: https://yutengfei.com/en/journal/project-material-review/ - Version: V1.0 - Published: 2026-10-19 - Revised: 2026-10-19 - Content status: Full text published - Content type: Methods (methods) - Research topics: Stakeholder Capital Governance (stakeholder-governance) - Ecosystem perspectives: Resource Ecosystem (resource) · Operations & Management Ecosystem (operations) · Capital Ecosystem (capital) ## Use this resource **Purpose**: Project materials often arrive one piece at a time: an introduction, a few photos, then contracts, budgets, licences and different versions of a plan. Each tells us something, but their relationships may remain unclear. **Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify. **Methods · Steps, inputs and completion criteria** **Evidence and validation limits**: Use this method to organize project records and plan evidence follow-up. State the scope, traceable basis, and outstanding checks for each conclusion. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text. This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output. ## Full article Project materials often arrive one piece at a time: an introduction, a few photos, then contracts, budgets, licences and different versions of a plan. Each tells us something, but their relationships may remain unclear. Which company is doing the work? Which assets have been obtained? Is funding in place? What rights will the participants ultimately receive? These questions may still be unresolved. The more materials we have, the easier it is to follow their story. An industry chain, an organizational diagram and a development target may look complete together. To move forward, however, we still need to know what connects each relationship. I would begin with four things: **entities, assets, funding, and rights and obligations**. Who is doing it? What do they rely on? Where will the money come from and how will it be used? What rights and obligations correspond to each participant? These questions give the materials a place. They also help distinguish supported points, statements made only in a proposal, missing evidence and matters that cannot yet be assessed. ## 1\. Establish what this review must answer Before reading, clarify the question: is this a preliminary business review, preparation for a collaboration discussion, or development of a formal plan? Does it concern a group, one company or a specific project? What date do the materials represent? Without that alignment, documents covering different scopes can easily be used to support each other improperly. A group introduction may not establish ownership of a particular project's assets. One project's operating results do not represent the group's financial position. An old document may explain history, but its current relevance still needs checking. I first write one sentence: **Which question about which entity or project, at which stage, is this review intended to answer?** Then register filenames, providers, creation dates, versions, relevant entities/projects and intended evidential purposes. Mark unknown dates or versions explicitly; do not guess validity from the order in which files were sent. The system need not be complex at the outset. Every subsequent conclusion should have a traceable source. ## 2\. Who is doing what? An introduction may mention a group, brand, project, platform and several companies. Examine their relationships separately. Ask who initiates, operates, signs contracts, receives payments, holds assets and bears the obligations behind commitments. One entity may perform several roles, or the roles may be split. Make the correspondence explicit. If one company signs and another operates, identify their collaboration arrangements, each party's authority to make commitments, and how responsibilities connect. Appearing in one group diagram does not establish these relationships automatically. Keep two levels of records: each entity's identity, and the relationships between entities. Registration documents may establish identity. Shareholding, control, cooperation and authorization each require evidence matching the relationship. A diagram explains intended design, but documents must still distinguish an existing structure from a proposed one. Once entities are clear, assets, funding and rights can be assigned to the appropriate parties. ## 3\. What assets support the work, and what is their current status? For each asset, ask what it is, where it is, who holds it, how far it is currently usable and how the project is connected to it. Already owned, used through cooperation, proposed for acquisition and planned for construction are different states. Record them separately even when they appear on one industry-development diagram. Equipment photos can show the site; they alone establish neither ownership nor use in the project. A proposed-acquisition list describes intended scope. Signing, satisfaction of conditions and completed handover require corresponding evidence. Beyond an asset's name, I focus on three items: - **Basis of acquisition or use:** ownership, lease, cooperation, proposed acquisition, or another specified arrangement. - **Current status:** discussions, signed agreement, completed handover, construction, trial operation or operation, recorded separately. - **Scope and conditions:** which entity may use it, during what period, for what activities, and subject to which limits or prerequisites. Operating figures must also match assets and periods. Design capacity, actual output, sales and cash collected describe different things. An expected capability must not become an operating result already achieved. This step establishes what the project actually relies on and which conditions the next step still requires. ## 4\. Where does funding come from, and how will it be used? Separate funding sources, uses and status. Planned total investment, planned external financing, and funds actually received and usable under their conditions are different amounts. A uses-of-funds table does not establish that funding is secured. An expression of intent, signed agreement, actual receipt and satisfaction of use conditions cannot all become one “completed” status. Trace who provides the money, who receives it, on what basis and under which conditions, and to whom it is then paid for which purpose. For transfers among companies or projects, check agreements, uses and records to prevent double counting the same money. Time matters too. Money received today may not cover every stage, and a long-term overall budget does not represent expenditure available in the current period. Clear statuses reveal whether the gap concerns a funding source, delivery conditions, a use budget or disbursement arrangements. Follow-up then becomes more specific. ## 5\. What rights and obligations does each participant have? “Participation”, “cooperation”, “partner” and “sharing” describe a direction. Actual arrangements need more detail. Does the participant receive services, payment for goods, business remuneration, project proceeds or long-term rights such as equity? Who owes the obligation, under what conditions is the right obtained, how is it recorded, and when and how is it fulfilled? Check each right's basis and treatment separately. Consumption, service cooperation, funding contributions and equity participation do not convert into each other merely because they share a label. I examine three correspondences: **Contributions and rights.** What does the participant provide, what is agreed in return, and are the calculation scope and conditions explicit? **Commitments and responsible entities.** Who makes the statement in the introduction, who must actually perform, and what authority and agreement support it? **Rights and performance records.** After an arrangement is proposed, identify its stage, conditions already met and records still missing. Check duration, exit, transfer, breach and dispute arrangements against the applicable terms. Where evidence is insufficient, keep the question open for the appropriate professional. Promotional language must not fill the gap with a conclusion. ![Figure 1: Checking entities, assets, funding and rights](https://yutengfei.com/journal/project-material-review/materials/en/asset-01.svg) _Figure 1 checks relationships within the same matter. Lines indicate correspondences to verify; they do not establish asset acquisition, receipt of funds or effective rights._ [Download Figure 1 SVG](https://yutengfei.com/journal/project-material-review/materials/en/asset-01.svg) ## 6\. Connect the four questions and find the breaks After answering them separately, check them together. Consider this set of materials. **The scenario illustrates the method only and represents no real project.** An introduction says the project plans to start production; an equipment list shows another entity holds the equipment; a cooperation agreement has outstanding effectiveness conditions; a budget includes equipment investment; participant materials describe sharing future operating results. Together, these describe an arrangement proposed for advancement. They do not yet connect how the equipment enters the project, whether conditions are met, who pays, who receives operating results or how participants benefit. The assessment should therefore be specific: equipment lists and cooperation materials exist, but some acquisition/use conditions remain unconfirmed. Do not state that the project has fully acquired the assets and meets every operating requirement. The next evidence is then clear: acquisition/use authority, records showing conditions were met, payment arrangements and formal explanations of participant rights. **An absent document does not establish that an arrangement does not exist. A description in a document does not establish that the stated current position is adequately supported.** Keep both distinctions in mind. ## 7\. Turn missing evidence into answerable, checkable requests “Materials incomplete” offers little direction. Another batch of introductions may arrive without resolving the original questions. Specify the fact to confirm, evidence required, provider and criterion for accepting the supplementation as sufficient. A practical order has three levels: | Priority | Resolve first | How to use it | | --- | --- | --- | | First: core judgments | Material gaps in entity relationships, key assets, funding sources and rights conditions | Obtain key evidence before making decisions based on it | | Second: execution | Business details, itemized budgets, schedules, delivery conditions and responsibilities | Add items as execution is designed, checking consistency | | Third: presentation and archiving | Clear attachments, consistent names, captions, versions and indexes | Assemble a usable package once core facts are clear | This is a working order, subject to each issue's importance. A licence, technical conclusion or professional confirmation that determines whether work can proceed belongs earlier; it cannot mechanically be left as an attachment to obtain later. For every gap, record at least **question, evidence required, provider, current status, expected date and acceptance result**. If a person or date is unconfirmed, mark it “to be determined”. Do not promise on someone else's behalf or turn unknowns into settled facts to make a table look complete. Recheck new materials for entity, applicable date/version, scope of support and conflicts with older documents. Receiving a file and resolving a question are separate statuses. ![Figure 2: From receipt and four-question checks to evidence requests and stage assessment](https://yutengfei.com/journal/project-material-review/materials/en/asset-02.svg) _Figure 2 connects gaps, additional evidence and acceptance. Insufficient key evidence may allow only a clearly limited interim judgment; pending matters must not quietly become affirmative conclusions._ [Download Figure 2 SVG](https://yutengfei.com/journal/project-material-review/materials/en/asset-02.svg) ## 8\. Make the handover usable After one review cycle, the next person should see the evidence available, gaps remaining, possible next actions and matters that still cannot be determined. Deliverables can be simple: entity/relationship, asset-status, funding-arrangement and rights tables, with source indexes and evidence requests. Label the nature of each important conclusion: - For a source statement, identify the document making it. - For checked content, specify the scope and date verified. - For calculations, retain units, calculation basis and assumptions. - For unfinished plans, retain conditions and current status. - State recommendations from this review separately from existing arrangements. This lets another person continue, revise plans or add materials. If new evidence changes the interpretation, the relationships show where updates are needed. This also reflects my approach of “complexity, simplicity, ease and diagrams”: lay out materials and relationships, identify the few questions affecting outcomes, turn them into checkable steps, and show the steps and relationships visually. ## Closing Understanding a project means connecting scattered materials to the same matter. Clear entities identify responsibility; asset status shows what supports advancement; funding arrangements expose conditions and gaps; clear rights let participants understand what they are joining. Start by listing evidence and questions under these four headings. Say only what can be confirmed, and assign remaining evidence requests to specific people. That gives subsequent action a basis. [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training. [AI usage guide](https://yutengfei.com/en/journal/ai/) --- # Understanding a Project Through Four Chains: Entities, Assets, Funds and Rights - Author: Andrew David W.Y. - Source: https://yutengfei.com/en/journal/project-four-chains/ - Version: V1.0 - Published: 2026-10-19 - Revised: 2026-10-19 - Content status: Full text published - Content type: Models (models) - Research topics: Stakeholder Capital Governance (stakeholder-governance) - Ecosystem perspectives: Resource Ecosystem (resource) · Operations & Management Ecosystem (operations) · Capital Ecosystem (capital) ## Use this resource **Purpose**: A project presentation can describe an ambitious industry, a platform, partners and a development path. Yet when the team tries to move forward, a few questions may still be unclear: who signs, who owns the assets, who receives the money, and who is responsible if something goes wrong? **Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify. **Models · Elements, relationships and assumptions** **Evidence and validation limits**: The example illustrates how to analyze the situation and use the approach. When applying it, substitute actual business records for the example conditions and check the judgment and outcome. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text. This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output. ## Full article A project presentation can describe an ambitious industry, a platform, partners and a development path. Yet when the team tries to move forward, a few questions may still be unclear: who signs, who owns the assets, who receives the money, and who is responsible if something goes wrong? I think these questions offer a useful starting point. Lay out four chains: entities, assets, funds and rights. Then examine whether they correspond. What does each name refer to? What does each connection mean? Which document supports it, and what stage has the arrangement reached? Once these matters are clear, there is a basis for discussing the details. **A diagram can show a complete set of relationships. Evidence determines how much we can say about those relationships.** ## 1\. Examine the four chains separately first Each chain answers a different question. | Chain | First question | Follow-up questions | | --- | --- | --- | | Entities | Who participates, signs and takes responsibility? | How are the parties related, and where does their authority come from? | | Assets | What assets or rights does the project involve? | Who controls them, how were they obtained, and what conditions or restrictions apply? | | Funds | Where does money come from, through whom does it pass, and where is it used? | What remains planned, what has been secured, and what supports each payment? | | Rights | What does each participant obtain, and who must fulfil the corresponding obligation? | When and under what conditions are rights obtained, and how are they recorded, fulfilled or exited? | Separating the chains helps explain matters of different kinds. We then need to bring them back together around the same transaction or activity. One company may perform several roles, and several companies may divide the work of one business activity. What needs explaining is the basis for those arrangements and the part for which each party is responsible. ![Figure 1: Four chains and their cross-checks—entities, assets, funds and rights](https://yutengfei.com/journal/project-four-chains/materials/en/asset-01.svg) _Figure 1: The four chains are four perspectives for review. A connecting line identifies a relationship to establish; it does not imply a transaction sequence or that the relationship already exists. E01–E08 are illustrative evidence IDs._ [Download the editable SVG framework](https://yutengfei.com/journal/project-four-chains/materials/en/asset-01.svg) ## 2\. Entities: who is actually doing the work behind each name? Project materials may mention a group, a business brand, an operating platform, a project company, partner organizations and a preparatory team. Distinguish what each name represents before discussing the relationships between them. For every name, I suggest adding three pieces of information: what it is, what work it undertakes, and who can make the relevant arrangements on its behalf. If it is a company, verify the specific legal entity. If it is a brand, business division or working name, label it accordingly. Do not automatically treat it as the contracting party or recipient of funds. A partner's name in a presentation also requires confirmation of the scope and current status of the cooperation. Then follow the relationships: who provides capital, who manages, who operates, who signs and who performs the obligations? Which relationships involve control, cooperation or delegation? What authorizes the person signing on an entity's behalf? A shareholding chart may answer some of these questions. The business activity itself also needs corresponding agreements, authorization and records of actual performance. Pay particular attention when the project is introduced under one name, the contract uses another entity and a third party receives payment. Different roles do not by themselves establish a problem, but the connections between them must be explained. ## 3\. Assets: what is their current status? When reviewing assets, I would separate “what is involved” from “how it may be used.” A machine, premises, technology, an order and an arrangement for project income are different things. Ownership, a right of use, eligibility to cooperate and a proposed acquisition also create different operating conditions. At a minimum, an asset record should identify the object, the relevant entity, how it was or will be obtained, and its current status. Add the scope, term, conditions of use and known restrictions where needed. If an acquisition is proposed, say so. If an agreement is signed but its conditions remain unmet, retain that status. If delivery and use have begun, check the corresponding records. Clear status descriptions are more useful than placing everything inside a box labelled “group assets.” Check the scope of the evidence too. A photograph of equipment may help identify the object; the photograph alone does not establish ownership. An expression of intent may show the direction of discussions, but it does not replace evidence of a completed acquisition. If a document is absent from the materials supplied, record “not included in this set of materials; further information required.” State the gap before drawing a conclusion about whether the enterprise has the asset or the relevant right. ## 4\. Funds: examine each step after establishing the total Funding figures are easily mixed. Record the total project budget, proposed funding for the current round, expressions of interest, committed amounts, funds actually received and funds eligible for use separately. The same money appearing at several steps must not be counted as several sources of funding. If the group receives money and transfers it to a project company, that is a movement between entities. Define the reporting scope and avoid double counting. For each amount, I would continue checking: who provides it, who receives it, what authorizes receipt, which conditions allow payment, what it will ultimately fund and who checks its use? Where money is expected to flow back later, specify the source, payment obligation, calculation basis and conditions. Planned sales or operating income remain plans. A return arrow in a diagram does not demonstrate that distributable funds already exist. The main task is to distinguish plans, agreements and events that have actually occurred. Only then can people discuss a funding gap, disbursement progress and implementation on the same basis. ## 5\. Rights: what does participation actually provide? Participation may provide equity, a contractual income-sharing arrangement, goods, services, business benefits or other rights. Explain each separately. Terms such as “partner,” “business partner” or “long-term co-builder” may help describe a relationship. The specific rights still depend on the corresponding arrangements. I think at least five questions need answers: 1. Who holds the right, and what exactly is it? 2. Who carries the corresponding obligation? 3. Under what conditions is the right obtained, and when does performance begin? 4. Which records confirm it, and how are discrepancies reviewed? 5. If the original plan cannot proceed, how are adjustments, termination or exit handled? Record different forms of participation separately. Calling them all “investment” or “cooperation” does not make the rights identical. In particular, reconcile funds with rights. Who receives the money and who owes the relevant obligation are two questions to check. If they are different parties, establish the basis connecting them. A sentence of assurance in a presentation cannot replace that connection. ## 6\. Bring the four chains together to find the gaps Here is a wholly fictional equipment project. Its entities and arrangements are created for teaching and do not refer to a real enterprise. Suppose Project Company A plans to build a production line. Operating Company B will run production, Supplier C will supply equipment, and Partner D proposes to provide funding. The presentation says D is acquiring equity in A. An existing draft contract names B as the payment recipient. A signs the equipment procurement draft, while a separate note proposes that B may use the equipment. These materials allow us to ask questions. They do not yet establish all the relationships as effective. - **Entities and funds:** Why would D pay B? If B collects on A's behalf, the authority and accounting arrangements need to be clarified. - **Funds and rights:** How does D's payment correspond to equity in A? Explain the obligated party, acquisition conditions and confirmation procedure separately. - **Entities and assets:** Who purchases, receives, controls and uses the equipment? Check the scope of the contracts and the subsequent delivery records. - **Assets and rights:** Does B's proposed use of the equipment support the production responsibilities it undertakes? What are the scope, term and outstanding conditions? Update the assessment if later materials reconcile these matters. Retain an unresolved status for remaining conflicts. This review tells the team what to ask next and whom to approach for further information. A complex structure can be explained, provided its connections have an adequate basis. ## 7\. Give each important connection an evidence ID When drawing the diagram, I suggest numbering important connections. A discussion of a particular relationship can then go straight to the relevant materials, without searching the entire file set again. The IDs in Figure 1 can be used as follows. | ID | Connection to explain | Materials to examine | | --- | --- | --- | | E01 | Participating entities and their control or cooperation relationships | Entity information, shareholding or cooperation arrangements and their current status | | E02 | Authority, contracting parties and parties responsible for performance | Authorization, signing capacity and corresponding responsibilities | | E03 | Asset objects, acquisition method and status | Ownership or acquisition evidence, agreements and explanations of conditions | | E04 | Current status and the scope of control or use | Delivery records, use arrangements, terms and restrictions | | E05 | Funding sources, receipt and disbursement conditions | Funding agreements, secured status and the basis for receipt and disbursement | | E06 | Disbursement, actual use and arrangements for funds to flow back | Payment records, evidence of use, budgets and repayment or return arrangements | | E07 | Rights holders, obligated parties and acquisition conditions | Rights provisions, corresponding obligations and conditions | | E08 | Conditions, registration, performance and exit | Applicable confirmation records, evidence of performance and subsequent handling arrangements | An ID is a locator. Whether the material is valid, which entity and period it concerns, and how much it supports still depend on its content. One document may support several connections; one connection may require several documents. After receiving an attachment, keep “received” separate from “reviewed.” ## 8\. What happens after a gap is found? First make the intended conclusion specific. For example: “A has obtained the right to use this equipment,” or “this payment has reached the agreed recipient.” A specific conclusion makes the necessary evidence easier to define. Then check whether four things correspond: the entity, object, status and period. If they do not yet correspond, add the issue to a gap register. Distinguish missing information, conflicting materials and an event that has not yet occurred. They require different next steps and should not all be labelled simply “to be improved.” For missing information, state what is needed. For a conflict, ask the relevant parties to reconcile the descriptions and supporting evidence. For an event that has not occurred, retain a planned or pending status. Give each gap an owner, a list of required materials and a review point. Recheck when the information returns, and limit the conclusion to what the evidence supports. ![Figure 2: Cross-checking the four chains, addressing gaps and updating conclusions](https://yutengfei.com/journal/project-four-chains/materials/en/asset-02.svg) _Figure 2: Return to review after obtaining further evidence. Where the materials correspond, form a working assessment with a defined scope. Changes in entities, terms or performance status require a further update._ [Download the editable SVG mechanism diagram](https://yutengfei.com/journal/project-four-chains/materials/en/asset-02.svg) Keep the conclusion, evidence and unresolved matters in the same version of the record. When something changes later, the team can identify which connection needs rechecking and which external statement needs updating. ## 9\. A project becomes easier to advance when it can be explained Understanding a project means turning scattered materials into relationships that people can question, trace and update. The entity chain identifies responsibility. The asset chain shows the operating basis and conditions of use. The funding chain explains how resources are secured and used. The rights chain explains what each party receives and undertakes. Cross-checking these chains moves the discussion from “this is a good project” to specific conditions and actions. The framework helps organize facts, identify gaps and coordinate the next step. Specific questions of ownership, transaction validity, finance or other professional matters still require the appropriate people to assess the actual materials. What matters most to me is whether, after drawing the diagram, the team can say accurately: what do we know, what do we still not know, and who will establish which fact next? That is when the diagram starts doing useful work. [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training. [AI usage guide](https://yutengfei.com/en/journal/ai/) --- # Building an Industry Digital Platform in Verifiable Stages - Author: Andrew David W.Y. - Source: https://yutengfei.com/en/journal/phased-industry-digital-platform/ - Version: V1.0 - Published: 2026-10-19 - Revised: 2026-10-19 - Content status: Full text published - Content type: Playbooks (solutions) - Research topics: Stakeholder Capital Governance (stakeholder-governance) - Ecosystem perspectives: Resource Ecosystem (resource) · Customer Ecosystem (customer) · Operations & Management Ecosystem (operations) ## Use this resource **Purpose**: Define the first release around one verifiable business process, including its states, role permissions, and exception handling. Review four stages, assess system delivery and operating results separately, and use both to decide whether to expand. **Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify. **Playbooks · Objectives, combinations and implementation conditions** **Evidence and validation limits**: The example illustrates how to analyze the situation and use the approach. When applying it, substitute actual business records for the example conditions and check the judgment and outcome. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text. This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output. ## Full article When an industry proposes a digital platform, it is easy to list functions: procurement, orders, inventory, delivery, settlement and reporting. After making the list, we still need to answer which problem the first phase will solve, who will actually use it, how a business event will be completed, who handles errors and what will demonstrate that the work is done. I think we can start with one real business process and make it a working system with clear boundaries and someone ready to operate it, then expand. The first phase may cover one type of business and a small number of parties. It should still connect initiation, delivery, exceptions and reconciliation. Explain which steps the system supports and which remain manual. **Build in stages, and assess system capability separately from business outcomes.** Here is a reference arrangement to adapt to the activity concerned. ## 1\. Identify the business problem before defining the first phase Start with a recurring problem. Perhaps buyers and suppliers use different specifications, confirming orders requires repeated calls, or delivery records do not match reconciliation records. Examine these situations to identify the step needing change, the roles involved and what a platform can undertake. Be specific. Who initiates the activity, confirms supply, delivers and checks the result? What does each step receive and produce, and whose confirmation must it await? Once those relationships are clear, determine the first-phase functions. A “minimum scope” means a complete business process that can be examined independently. It need not include every product category or region, and effective manual practices can remain. Within that process, however, there should be a place for normal work, changes, authorized confirmation and reconciliation. Otherwise, the pages may be built while people still have to connect the actual work informally. State what this phase excludes. Register other requests and why they may be useful later, rather than turning every discussion directly into a new task. A baseline record is also useful: which actions previously confirmed a transaction, where errors occurred and who carried extra coordination work. This provides a basis for later comparison. ## 2\. Connect business statuses, roles and records For an ordinary fulfilment process, begin with four steps: request, supply confirmation, fulfilment and delivery, and reconciliation confirmation. Each step should answer who acts, on what basis and what record remains. A request does not mean that a supplier has committed. A delivery still requires checking receipt, discrepancies and settlement conditions. Keep these statuses separate so users can see where the activity stands. Link related records through business IDs. A request may become several orders, an order may have partial deliveries, and several events may be reconciled together. Preserve individual records and their relationships. I would avoid using a single “completed” status to cover all these matters. Delivery, reconciliation, receivables and cash received can be checked separately; a green indicator on a screen is insufficient. Identify who maintains the information. If specifications, units, supply conditions or delivery dates change, who confirms the new version, which outstanding activities are affected and how will users know? **Information reaching the next step is only part of the job. Someone must be responsible for its meaning, origin and scope.** ![Figure 1: A verifiable platform workflow around one real business process](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-01.svg) _Figure 1 is a general reference architecture. Documents are linked by their business relationships. Partial deliveries, changes and disputes require separate handling; one order need not correspond to one delivery or one receipt of payment._ [Download Figure 1 as SVG](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-01.svg) ## 3\. Include permissions, exceptions and reconciliation in the first phase A process working in a demonstration still needs to be examined against its users and possible changes. Permission to view information does not necessarily include authority to confirm an order. Permission to enter data does not allow someone to change another party's result. Arrange viewing, entry, confirmation, amendment and export separately according to actual responsibilities. Use only information the team is authorized to use and needs for this activity. Assign responsibility for its source, updates and error correction. Keep the corrected result distinguishable from the original evidence. Design exception handling too. What status follows a changed requirement, insufficient supply, partial delivery, a quantity discrepancy or disagreement over reconciliation? Who takes over? If every error can only be resolved by a developer changing data behind the scenes, frontline users struggle to understand what happened and later review loses its basis. Provide handling routes for common exceptions. Record the facts, assign an owner, retain the handling and confirmation records, then return to the appropriate step. Keep unresolved matters pending rather than forcing confirmation to close the workflow. Check easily missed cases: can a repeated delivery submission create a duplicate? Can other steps see a withdrawal or correction? Are old permissions adjusted when a person leaves their role? These matters directly affect reliable operation and belong in first-phase acceptance rather than being postponed indefinitely. ## 4\. Advance through four stages, with evidence for each transition ### Stage one: define the problem and acceptance scope Agree the problem, this phase's boundaries, participating roles, current conditions and separate system and business checks. Confirm the scope, necessary records, permissions, principal exceptions, owners and resources together. At this stage, the business and implementation teams should be able to use the same process diagram to explain the start and end, human confirmations and system processing. ### Stage two: complete the bounded workflow In a controlled environment, test normal activity and the main exceptions. Actually perform each step: can it be executed, who may confirm it, does the data have corresponding evidence, and can errors be found and corrected? When a problem appears, record what happened, the affected step and the person responsible for correction, then recheck. A ticked feature list is not enough. Manual steps with explicit boundaries are acceptable, provided there is an owner, a recordkeeping method and a view on future adjustment. Do not move a scope into live use while gaps affecting critical activity remain unresolved. ### Stage three: trial within the confirmed scope After system checks pass, admit limited real activity and participants. Arrange daily support, issue response, information checks and fallback procedures for failures. During the changeover, identify the primary business record and how differences will be handled. If short-term parallel checking is necessary, agree its purpose, owner and ending conditions. Do not indefinitely require frontline staff to enter the same activity twice while excluding the extra work from costs. Collect system performance and business changes separately. Being able to record and confirm is one result; less rework, shorter waits and better reconciliation are another. If critical permission, record or fulfilment problems prevent processing under the confirmed conditions, suspend the relevant new operations and use the agreed fallback for necessary work. Reconcile discrepancies, retest affected scenarios and obtain authorized confirmation before resuming. ### Stage four: establish stable ownership before reviewing expansion Once this process is stable, someone must formally take over daily operation. Assign actual owners and usable instructions for business rules, staff and permission changes, issue response, costs, and information export, retention and recovery. Test the handover. Can the receiving team complete a transaction and handle the main exceptions? Can they find a fallback during a failure? Can backed-up information actually be restored and reconciled? Then consider adding categories, participating nodes or regions. Review the new volume, information differences, support costs and responsibilities. ![Figure 2: Phased construction, separate acceptance and expansion review](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-02.svg) _Figure 2 organizes stages around delivery and acceptance conditions. Reaching a date or launching a function does not automatically authorize the next stage. A system may pass while business outcomes remain under observation._ [Download Figure 2 as SVG](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-02.svg) ## 5\. System acceptance and business acceptance answer different questions I think the key distinction is between what the system can do and what consequently happened in the business. | Acceptance area | Main checks | Possible evidence | | --- | --- | --- | | System capability | Executable workflow, correct permissions, traceable records, and ways to handle exceptions and failures | Normal and exceptional operation records, permission checks, reconciliation and recovery tests | | Business outcomes | Actual use, changes in delivery and reconciliation, rework, waiting, costs and burdens | Before-and-after records, participant feedback, inputs and issue-resolution records | These conclusions need not be forced into one “pass.” If the system supports the bounded process but the observation period is insufficient, retain “outcomes under observation.” Where agreed system conditions and business responsibilities are satisfied, limited use may continue while expansion is deferred. Conversely, an apparently improved business period does not remove important permission, data or exception problems. People may have added substantial coordination effort, or other conditions may have changed. One favourable result should not conceal these issues. Define the comparison: included activity, period, what counts as rework, and how extra hours and expenses are recorded. Use consistent definitions where possible. Volume, order complexity, supply conditions and prices may also affect results. Record these changes to improve judgment, without expecting one limited trial to establish every causal relationship. An acceptance conclusion can be specific: what is usable, what remains unresolved, who handles it, what cannot yet be confirmed and when the team will return to check. ## 6\. A fictional industrial-consumables example This situation was written for illustration. It does not describe a real enterprise or an achieved implementation result. Several manufacturers and their supply and delivery partners want to improve inquiries, delivery and reconciliation for common industrial consumables. The first phase can be limited to one category of standard consumables, a defined group of participants and one fulfilment chain, rather than all procurement and management activities. Clarify specifications, units and delivery conditions first. Supply confirmation creates the corresponding business record. Delivery and receipt link to it; partial arrivals, quantity differences and reconciliation opinions retain separate statuses. | Stage | Initial deliverable in this example | How to check | | --- | --- | --- | | Define scope | One process from request to reconciliation, roles and acceptance definitions | Can parties explain responsibilities, inputs, outputs and phase boundaries? | | Complete workflow | Normal ordering, supply confirmation, partial delivery and discrepancy handling | Can people act by role, and can quantities and records be reconciled? | | Controlled trial | Limited live activity, issue support and fallback procedures | Who actually uses it, does it add duplicate work, and how are issues resolved? | | Handover and expansion | Daily ownership, maintenance arrangements and review materials for the next scope | Can the receiving team operate independently, and does expansion have resources and evidence? | If specifications are clearer but reconciliation still requires manual reaggregation, trace that step. Are records unlinked, definitions inconsistent or responsibilities unclear? Revise accordingly. If one group can use the system normally while another needs extensive extra support, the conditions for use need further clarification. Examine the differences before maintaining the limited scope, retesting after changes or deferring expansion. Feature construction, real use, daily handover and operating improvement remain connected but separately assessed. ## 7\. Revisit costs and responsibilities before expanding A platform can usually do many more things. Every added scope may also create information maintenance, training, support and exception-handling work. Include continuing operating costs in expansion review. Who pays for development, information preparation, role training, daily support, process changes and maintenance? Separate premises, equipment and fulfilment inputs by actual use rather than putting them all into a software-development budget. Establish what existing systems can provide before deciding how to fill gaps. This approach does not presume that a particular software package must be replaced or that every industry needs the same technology. More features, nodes and records still need to be assessed in actual activity. Whether they help the parties work more clearly and reliably provides a basis for further investment. Before the next stage, ask: 1. Which business process has this phase actually connected? 2. Are normal and exceptional situations owned and supported by checkable records? 3. What has been established about system capability and business outcomes separately? 4. Who can take responsibility for daily operation, failures and information maintenance? 5. What resources, responsibilities and authority does the next scope need? Move forward with clear answers. Leave matters without adequate evidence pending review or validation. A platform can be built process by process. Each part that can be delivered, used and taken over provides a basis for the functions and scale that follow. * * * [Download the accompanying Phased Construction and Acceptance Checklist](https://yutengfei.com/journal/phased-industry-digital-platform/materials/en/asset-03.md) [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training. [AI usage guide](https://yutengfei.com/en/journal/ai/) --- # Project evidence ledger: trace every conclusion to its sources - Author: Andrew David W.Y. - Source: https://yutengfei.com/en/journal/project-evidence-ledger/ - Version: V1.0 - Published: 2026-10-19 - Revised: 2026-10-19 - Content status: Full text published - Content type: Tools (tools) - Research topics: — - Ecosystem perspectives: Resource Ecosystem (resource) · Customer Ecosystem (customer) · Operations & Management Ecosystem (operations) · Capital Ecosystem (capital) ## Use this resource **Purpose**: Assign separate IDs to claims and records, and log what each record supports, its version, the review result, and the follow-up owner. Delivery and distribution examples show how to trace claims back to evidence and find affected statements when evidence changes. **Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify. **Tools · Fields, records and interpretation rules** **Evidence and validation limits**: The table and fictional entries show how to retain evidence and review records. When using it, log the document version, reviewer, and outstanding checks. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text. This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output. ## Full article As a project moves forward, its materials usually multiply: plans, contracts, spreadsheets and chat records, stored on computers and shared in groups. Yet when someone asks where a number came from, how far a task has progressed, or which document supports a claim, the search often starts again. Finding a file does not always mean finding an answer. A target in a plan may become reported progress. An internal record of goods leaving the warehouse may become “delivery completed” in external materials. The documents are still there, but the meaning has been stretched along the way. I think this calls for a ledger linking statements to their supporting materials. Before a statement is used, establish what it says, where its evidence is, how far that evidence supports it, and what remains unverified. When the materials change, follow those links to update both the conclusion and its citations. ## 1\. Write down the statement to be checked Organizing files into folders is useful, but take one further step: what exactly do we intend to say on the basis of these files? Copy the original sentence proposed for a plan, webpage, report or introduction, and assign it a claim identifier. Here, a “claim” is a statement awaiting verification; the identifier does not establish that it is true. Specify its subject, time, scope and basis. For “completed”, which batch, which stage, as of what date, and confirmed by whom? Without those details, even many documents may fail to match. Check each action in a sentence separately. Warehouse dispatch, receipt and acceptance each require their own evidence. Verifying dispatch alone does not allow you to tick off receipt and acceptance. Keep the original sentence to show what was initially said, but split it into separately assessable items. Formal wording must stay within what is actually supported. The same applies to figures. Amounts need units, percentages need a base, cumulative figures need a period, and plans must remain separate from actual results. Accurate wording gives the search a clear direction. ## 2\. Give claims and evidence separate identifiers I suggest recording claims, evidence and the verification links between them separately. Use C identifiers for claims, E for evidence and L for links. C01 r1 is the first revision of a claim; E01 v1 is the first version of a document; L01 records how that claim revision uses that evidence version. Adapt the numbering to the team’s practice, but keep it stable. Changing a sentence must not overwrite its earlier record. Why record links separately? One conclusion may require several documents, and one document may be cited by several conclusions. A whole file cannot simply be labelled “verified”. Its support must be assessed for each specific claim. For example, a dispatch record may help establish quantity without establishing receipt. The same document in three folders still has one source; it is not three independent confirmations. Record exact locations too. For a PDF, state the version, physical file-page sequence and relevant passage; add the printed page number if it differs. For a spreadsheet, give the sheet, row or record ID. “See attachment” leaves the next person searching again. ![Claims, evidence and limits of support](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-01.svg) [Download SVG: Claims and limits of evidential support](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-01.svg) ## 3\. Separate three easily confused statuses Receiving a document establishes that it has been obtained. Checking its contents establishes that certain checks were performed. Whether a statement may be used externally still depends on its wording, audience, channel and approval authority. Record these three matters separately. | Question | What to record | What does not follow | | --- | --- | --- | | Have the materials arrived? | Not provided, partly received, received, and other acquisition statuses | Receipt does not establish authenticity, completeness or continuing validity | | How far has this statement been checked? | Pending verification, partially supported, supported within a defined scope, conflicting, and other verification statuses | Checking part does not establish the whole statement | | Where may this text version be used? | Not approved, approved for limited use, review required, and other use statuses | An internal judgment is not permission for public disclosure | Also record the nature of the claim and form of evidence. Is the claim a fact, target, calculation or analysis? Is the document an original, copy, screenshot or draft plan? These affect the checks needed, but do not determine truth automatically. The ledger needs no “pass” button that automatically turns green. A defined scope is more useful than an unqualified “confirmed”. ## 4\. Keep conclusions within the support available For each statement, I look at two fields together: what is supported, and what is not yet supported. The first preserves the value of existing evidence; the second prevents overstatement. Record conflicts specifically: different subjects, periods or bases, or two accounts of the same event? Identify the difference before deciding what to obtain next. **Both examples below were newly written for teaching and are fictional. Their materials, roles, values and 2030 scenario dates represent no real project. They demonstrate verification methods, not actual business records.** ### Example 1: Can 12 display stands be described as “delivered and accepted”? The original claim is: “The 12 display stands in this batch have been delivered and accepted.” Open E01 and find record ID OUT-07. The first row records 12 stands as dispatched from the warehouse. Neither receipt confirmation nor acceptance records have been provided. The evidence currently supports only that the simulated internal record states that 12 items were dispatched. It does not yet establish receipt or completed acceptance. Mark C01 “partially supported”. Next obtain receipt confirmation and acceptance records, and check the entity, batch, scope and dates. For internal review, narrow the wording to: “The simulated internal records for this batch state that 12 display stands were dispatched from the warehouse; receipt and acceptance remain to be verified.” This wording is still not approved for external use. Missing acceptance records in this batch do not establish that acceptance never happened. The current conclusion is “not yet verified”. Do not turn missing documents into a negative claim about reality. [Open E01: Simulated dispatch record](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-02.md) ### Example 2: Why does an unchanged 15% produce two results? The original claim is: “The materials-organizing subsidy has been set at 1200 exercise units.” Draft A, E02, uses a base of 8000 exercise units: 8000 × 15% = 1200. Draft B, E03, uses a base of 2000: 2000 × 15% = 300. Both calculations can be arithmetically correct, while the choice of base remains unresolved. Both documents are drafts, with no evidence of approval or effectiveness and no formal statement that one supersedes the other. B is dated one day later; that alone does not make it effective. Mark C02 “conflicting”. Keep the two inputs, recalculations and limits of support separately in L02 and L03. Retain this internal wording: “Recalculation using the different bases in two simulated drafts produces 1200 and 300 exercise units respectively; the adopted base, approval and eligibility conditions remain unconfirmed.” Arithmetic shows how a result follows from given inputs. Whether the inputs were approved, to whom they apply, and whether eligibility conditions are met need separate checks. A calculator result cannot replace confirmation by an authorized person. [Open draft A](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-03.md) · [Open draft B](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-04.md) · [View both completed fictional examples](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-05.md) ## 5\. Link gaps to people and next actions “More information needed” often leaves the work where it was. State exactly what is needed, which role is proposed to provide it, who will follow up and review it, and when it is planned to be checked again. If nobody has been assigned, write “proposed follow-up by \[role\], pending assignment”. If the date is unconfirmed, leave it to be determined. Do not make commitments for others merely to fill the table. Record planned dates and actual action dates separately; reaching a planned date does not complete the work. Specify the review action too: locating an original passage, checking applicability, recalculating, or comparing documents. Record the action and result so that others can understand how “partially supported” was reached. Some questions require financial, legal, technical or other professional work. The ledger routes them appropriately and retains the response. Its working statuses do not replace professional due-diligence conclusions. ## 6\. When materials change, find where they were used The ledger must cover more than the first check. A new document may change an earlier statement and affect materials already distributed. Retain the old file and register the new version. Check what changed, the applicable scope, who confirms effectiveness, whether supersession is explicit, and how existing rights and conditions are handled. A later date or “final” in the filename answers none of these automatically. If a claim changes, retain the old revision and add a new one with its basis and verification date. Mark the current wording to which an old revision no longer applies, so that it is not reused directly as a current source. Return to use records and locate webpages, plans, presentations and downloads that cited it. Decide individually whether renewed review, suspension, text changes, attachment replacement or other action is needed, and record the actual result. Use approval must identify the exact text version, audience, channel and conditions. Permission for a sentence in one internal meeting does not permit publication on a public webpage. Completed verification also does not establish permission to display source materials publicly. ![Evidence updates, review and citation checks](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-06.svg) [Download SVG: Evidence, review and statement updates](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-06.svg) ## 7\. Start with one important conclusion There is no need to renumber every file at once. Choose one important, frequently cited statement and work through these steps. 1. Copy the original statement; specify subject, period, units and applicable conditions; assign a claim identifier and revision. 2. Register the materials, exact versions and locations, sources, duplication relationships and access scope. 3. Link each claim to each relevant document, recording support, gaps, conflicts and actual checking actions separately. 4. Form limited wording for internal review. List proposed additional materials, follow-up and review roles, and planned dates. 5. When use beyond the immediate review is genuinely needed, record the proposed text, audience, channel and approval basis. Recheck all citations after materials change. The tool has five tables: claims, evidence index, verification links, actions and changes, and use approvals and records. Start at the claim row and follow identifiers to documents and checking records. The relationships remain traceable as they multiply. The Excel workbook contains five blank tables and two fictional examples. Blank tables contain no prefilled names, statuses or approval dates. Examples are on separate sheets to prevent confusion with real records. CSV and Markdown versions are also provided for maintenance in other tools. [Download the editable Excel ledger](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-07.xlsx) · [Blank ledger and instructions](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-08.md) · [Field and status definitions](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-09.md) · [Update review and citation checklist](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-10.md) [Download SVG: Blank check for a single conclusion](https://yutengfei.com/journal/project-evidence-ledger/materials/en/asset-11.svg) ## 8\. Turn complex materials into checkable relationships This is a practical expression of what I call “complexity, simplicity, ease and diagrams”. First organize scattered materials, original statements, conditions and conflicts: address complexity. Then isolate the evidence and gaps relevant to one claim: simplify. Make numbering, locating, status recording, follow-up and review into actions another person can take over: make it usable. Finally, connect conclusions, evidence, supplementation, confirmation and citation updates in a diagram. The diagram must still let someone open the evidence, find the passage and explain the judgment. Keep unresolved questions, narrow overstated wording, and continue obtaining missing materials. The next person should be able to follow the ledger and see what supports a statement, how far it has been checked, and which role must confirm the next step. [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training. [AI usage guide](https://yutengfei.com/en/journal/ai/) --- # Draw the Project: A Four-Chain Evidence Exercise - Author: Andrew David W.Y. - Source: https://yutengfei.com/en/journal/project-four-chain-exercise/ - Version: V1.0 - Published: 2026-10-19 - Revised: 2026-10-19 - Content status: Full text published - Content type: Training (training) - Research topics: Stakeholder Capital Governance (stakeholder-governance) - Ecosystem perspectives: Resource Ecosystem (resource) · Operations & Management Ecosystem (operations) · Capital Ecosystem (capital) ## Use this resource **Purpose**: Use fictional evidence cards to map entities, assets, funds, and rights. Mark existing evidence and open questions in successive rounds, then compare judgments before and after new records arrive to practice turning gaps into concrete questions. **Conditions for use**: Check that the subject, objective and constraints fit the task. Confirm any conditions that the article does not specify. **Training · Learning goals, practice and feedback** **Evidence and validation limits**: This exercise uses fictional materials. Compare how participants reached their judgments and review the evidence they used after the exercise. No separate external-validation result is recorded for this article. Publication does not establish effectiveness; check the evidence, assumptions and limits in the text. This is a readable, citable knowledge resource, not an installed Skill. When using it with AI, retain its sources and limits and review the output. ## Full article A project introduction usually seems to contain everything: who leads it, who operates it, what equipment is involved, how much will be invested and what partners may share. After reading it, the project may feel clear. Yet several questions still need answers before moving forward: who contracts externally, who owns the assets, whose account received the money, and who must fulfil each commitment? I think drawing the relationships is a useful start. Every name and line needs a basis. Where the drawing cannot continue, stop and ask. This article provides a practical exercise. With a wholly fictional set of materials, draw an initial diagram, obtain further information, revise it and explain why your judgments changed. Work alone or with two or three people. Leave the reference answer until later so you have a genuine opportunity to think. ## 1\. What do the four chains examine? Entities, assets, funds and rights are separated to organize the review. They are the observation dimensions for this exercise. The drawing style may vary; the relationships and evidence should be clear. | Chain | First questions | What the diagram should show | | --- | --- | --- | | Entities | Who participates and takes responsibility, and how are they related? | Entities, working roles, contractual or control relationships and their basis | | Assets | Which asset, who owns or uses it, and what stage has been reached? | Specific objects, ownership and use, acquisition method, delivery and other unconfirmed statuses | | Funds | Who pays whom, how much, for what purpose, and with what status? | Payer, recipient, amount, nature, period and payment conditions; separate intentions, agreements and actual transfers | | Rights | Who may require what from whom, and under which conditions? | Rights holder, obligated party, content, triggers and performance status | The chains cannot be drawn in isolation. Compare the customer order's contracting party, the receipt record's recipient, the equipment agreement's user and the party responsible for performance. If names differ, ask why. There may be a documented agency, lease or cooperation arrangement, or the materials may be incomplete. Mark the location when evidence is not yet available. ![Figure 1: Cross-checking entities, assets, funds and rights](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-01.svg) _Figure 1 offers a way to read materials and draw relationships. Read solid lines, dashed lines and unverified markers together with the cited materials and specific performance status._ [Download Figure 1 as SVG](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-01.svg) ## 2\. Establish the exercise rules The setting is a packaging-service pilot. A, B, C, D and E stand for five fictional entities. Every document, transaction and amount was created for this teaching exercise. None is a real company record or voucher. There are three rounds. **Round one: read the initial packet and draw.** Use cards E01–E06 to record supported relationships while retaining uncertainties. **Round two: question the diagram and record gaps.** Exchange diagrams with a partner, or use the questions below if working alone. Specify what additional information each gap requires. **Round three: open the supplementary packet, revise and explain.** Read E07–E10, change specific connections, retain what remains unknown and produce an action list. Get paper or a worksheet ready. Even a few lines should be your own work. Comparing after drawing helps reveal where you moved too quickly. [Open the four-chain worksheet](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-02.md) · [Download the blank exercise diagram as SVG](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-03.svg) ## 3\. Round one: what can these six cards support? The initial packet contains document summaries, a unilateral expression of interest, presentation claims and a receipt record. Their evidential nature differs. Read them individually before joining them into a complete story. ### E01 | Project introduction Provided by Company A. The introduction says A leads the packaging-service pilot and B handles daily operations; equipment has been secured and cooperation funding is in place. It provides no shareholding relationships, equipment list or funding details. ### E02 | Equipment quotation Sent by Company C to Company B. It lists a sale price and specifications for packaging equipment, stating that it is for discussion and that the transaction method and terms depend on a formal contract. The initial packet includes no contract, payment or delivery evidence. ### E03 | Summary of a signed customer order Provided by Companies B and D. B will provide D with a batch of packaging services. D pays an RMB 80,000 advance, with subsequent settlement based on service and acceptance under the order. The initial packet includes no completion or acceptance materials. ### E04 | Simulated bank receipt record Provided by Company B. B's account received RMB 80,000 from D, identified as the service advance for the E03 order. The initial packet contains no other evidence of funds received. ### E05 | Unilateral cooperation-interest email Sent by Company E to Company A. E proposes investing RMB 200,000 and discussing a share in operating results. The recipient entity, nature of the funds, payment conditions, corresponding rights and exit arrangements await written agreement. The initial packet has no formal bilateral cooperation document or receipt record. ### E06 | Meeting excerpt Record of a discussion between A and B. A leads planning and B proposes to operate; specific duties, fees and authority depend on a separate signed document. The excerpt does not confirm A's shareholding in or control over B, or establish authority to dispose of equipment. ### Begin drawing Write the five entities separately and place the objects from the materials beside them. For every line, add the **relationship, status and evidence ID**. A signed order supports recording that contractual relationship. Whether services are complete, payment is settled or other conditions remain must be checked separately. Marking a whole document “complete” should not turn every matter mentioned into an accomplished event. Use dashed lines for proposals and “unverified” for unsupported relationships. Other legends are acceptable if a reader can understand the same system consistently. Produce three things in round one: an initial four-chain diagram, a gap list and a short explanation of what can and cannot currently be concluded. ## 4\. Round two: question the basis for each line Before polishing the layout, work through the lines with these questions. **What does A mean by leading the project?** Planning, operating or controlling another entity? Which card supports the relationship you drew? **How far does a quotation addressed to B establish the equipment arrangement?** What supports the quotation, signed transaction, payment, delivery, ownership and use respectively? **Why did the money reach this account?** Which order or agreement does it relate to? Have you counted the same funds again as another new source? **How much of the proposed cooperation is defined?** Who receives the funds, when are they payable, what rights follow, and what remains under discussion? **Does the rights chain identify responsibility for performance?** If the diagram says someone “may receive a result,” who must provide it, under what conditions and through which process? The unanswered questions are worth keeping. “Missing materials” is too vague. Specify, for example: the equipment acquisition method cannot yet be established; a formal agreement and delivery evidence are needed to determine whether the line should show purchase, lease or another arrangement. Then the person collecting materials knows what you are asking. ## 5\. Round three: how does further evidence change the judgment? After completing the initial diagram and gap list, open the [supplementary packet E07–E10](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-04.md). Do not delete the first diagram and start again. Retain it and record three changes: 1. Which unknown does a new card explain? 2. Which earlier judgment needs correction, and was it originally too broad? 3. What remains uncertain after the new materials, and what must be asked next? **Further evidence gives every judgment an opportunity to be corrected.** Some connections become clearer, broad statements split into separate matters, and some locations remain unverified. Explaining those changes matters more than adding nodes. Afterwards, open the [reference solution and assessment criteria](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-05.md). The reference diagram is available in that file and the collapsible area of the illustrated review page so you can work before comparing. ## 6\. What should you check in the reference diagram? Your layout may differ. Compare relationships, directions, statuses and evidence first. For entities, position at the top is not proof of control. For assets, physical location is not ownership. Trace funds to the payer, recipient and specific event. Show both the holder of a right and the party responsible for fulfilling it. Check the connections between chains particularly carefully. Does received money have a corresponding obligation? Has a use arrangement been expanded into authority to dispose of an asset? Has proposed funding become confirmed equity or an allocation too early? The following reference diagram is for after the supplementary review. It retains unresolved matters and distinguishes actual events, contractual provisions and arrangements not yet implemented. ![Figure 2: Reference four-chain diagram after supplementary evidence in the fictional packaging-service project](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-06.svg) _Figure 2 represents only this exercise's materials and does not replace verification in a real project. Funds received, performance pending, unpaid and undefined are different statuses._ [Download Figure 2 as SVG](https://yutengfei.com/journal/project-four-chain-exercise/materials/en/asset-06.svg) ## 7\. Turn the result into next steps Explain the project in ordinary language to someone who did not draw it. Start with relationships that can be confirmed, then the remaining gaps. Do not turn proposed arrangements into established facts while speaking. Choose the two or three gaps that most affect judgment. Write actions specifying the question, the role to approach, the document needed and the check to perform when it arrives. If the actual owner or timing is not agreed, retain a pending status. The exercise develops a way of working: lay out the materials, identify key relationships, state questions clearly, and communicate through both a diagram and an action list. A diagram that identifies gaps is already useful. It gives discussion a specific location and later evidence somewhere to go. Then try it with your own work materials. For each line, ask where the evidence is, whether the status is right and whether the other chains correspond. Draw what can be supported and retain questions for the next check. [CC BY-NC-ND 4.0](https://creativecommons.org/licenses/by-nc-nd/4.0/) Applies to original text unless otherwise stated; excludes third-party materials. Downloading or machine reading does not extend the existing license or separately authorize derivatives, commercial use or model training. [AI usage guide](https://yutengfei.com/en/journal/ai/)