Understand which resources a project actually needs
Connect the intended result, enabling function, existing assets, substitutes and useful amount.
When a project asks for money, tools, people, access or time and needs to understand what would actually change the result.
Business competence · Resources and project development · Public edition 0.1.0
A project proposes buying a server for repeated inference work. The assistant first forms the required operating period, workload and continuity.
The key relationship. Forms the resource need from what must become possible, before selecting a provider, financial instrument or other carrier.
An illustrative situation to adapt to your work. Read the complete cases ↓
You supply the context: research, a service, a creative project or a team’s work. Examples make the method visible; adaptation preserves the relationships that make it work while understanding the purpose, sources, people and means of your own assignment.
Tell your AI what you want to achieve, what already exists and a practical situation to address. Ask how this competence changes the work and which knowledge from your domain should participate. MAIOS provenance identifies the shared knowledge; you can use it directly in your AI or compose it with an existing kernel.
Adaptation examples in other contexts ↗A resource supplies a function. Money, hardware, an employee, a partnership or a platform can be different ways of supplying it.
This competence forms what is needed and why, including a useful amount and timing where the present knowledge supports them. A valid result can be that existing resources suffice or that quantification remains open.
Understand the intended capability, milestone or continuation, present assets, actual limiting relation and consequential time pressure. Do not derive the project need from a grant ceiling, provider bundle or familiar budget. A resource may be required to change a condition, preserve an operation or enable a new possibility. Keep distinct resultants separate when combining them would silently subsidize an unrelated objective through the same narrative.
Explain which resource changes which condition and makes which operation or result possible. Use that relation to understand the need, without requiring a form for every task. 'To grow' or 'for marketing' is insufficient when it does not identify the actual limiting relation. A cash need differs from valuation, expertise from headcount and distribution from a chosen platform. An eligibility condition may enable access without being the resource ultimately needed.
Distinguish an external resource gap from an asset not reached, a missing competence that can be formed, an unnecessary process demand or a real external dependency. Reuse and compose before assuming procurement. Computing capacity can be supplied by hardware, credits, infrastructure partnership, reduced cost or a changed architecture. Resource families can include data, evidence, attention, coordination, focused time, physical equipment or another function exposed by the work. Their current names do not close the field.
Where material, distinguish the continuity floor, transition runway and longer transformation horizon. The continuity floor has causal priority when its failure ends the work before later possibilities can exist; it does not become the whole purpose. A transition can use a bounded product, service, partnership or adoption milestone while preserving the wider direction. If an external return relation is needed, form an inspectable intermediate value bridge without making a capital provider the authority over the project's deeper purpose.
Identify minimum, sufficient amount, timing, duration and recurrence when knowable. An amount may be exact, bounded, scenario-dependent or unknown. Compare useful marginal capacity rather than maximizing the resource. When money is a useful translation, connect resource units, duration, unit cost and causally justified contingency. Keep that cash equivalent distinct from the function and from in-kind support; credits or contributed time are not money raised. Preserve the unknown that prevents responsible quantification.
Reach product architecture when delivery changes demand; research when current outside facts determine availability; funding expertise when the established need requires a financial route; qualified legal, accounting or other domain expertise when its actual mechanics matter. Expression follows the formed need. Acquisition, refusal, substitution or an unnecessary resource can change this method through their effect on the intended result. Successful fundraising alone does not prove the need was well formed. Stop when another pass changes no useful relation.
These cases illustrate situations, causal distinctions and choices you can adapt to your work.
The following cases are illustrative. They explain choices and conditions; they are not reports of observed adoption.
A project proposes buying a server for repeated inference work. The assistant first forms the required operating period, workload and continuity. Existing hardware, hosted credits, a partner or a changed architecture may provide the same function. It compares these relations using actual available facts. A purchase remains a separately selected effect; the first hardware label does not determine the need.
A team wants an external reporting service because reports take too long. Source inspection reveals that data, analytical knowledge and a writing method already exist but are not connected. The assistant forms the missing composition and estimates the remaining real execution need. The result may reduce procurement, or reveal a genuine external dependency that the previous request had obscured.
A small research project needs focused operating time now and infrastructure for a later public service. The assistant preserves the immediate continuity floor and the future service scenario without merging them into one budget story. A bounded intermediate demonstration can make the transition inspectable. Its resource consequence is learned from the work, without presenting the longer horizon as a verified present fact.
Forms the resource need from what must become possible, before selecting a provider, financial instrument or other carrier.
Ask what must be available, then how it could be supplied. A certification may permit an application; an application may seek infrastructure; infrastructure may enable a specific service period. Preserving these relations avoids treating the first visible prerequisite as the whole need. A useful result can retain several substitutable carriers while already establishing the function and reason.
If duration is unknown, identify what decision fixes it. If three delivery forms require different capacity, keep their scenarios distinct. An unquantified amount can coexist with a well-understood need. A sufficient amount is relative to the selected resultant and its conditions, rather than a universal upper limit. Revisit an estimate when a new capability changes the actual bottleneck.
This method forms understanding and preparation. Choosing a resource route does not by itself spend, hire, borrow, accept terms, contact an investor or submit an application. Use current qualified facts for a specific consequential proposal and the actual mandate for its effect. Keep sustainable attention, independence and recovery conditions visible when they materially change the proposed resource relation.
Understand which resources a project actually needs
A resource supplies a function. Money, hardware, an employee, a partnership or a platform can be different ways of supplying it.
This competence forms what is needed and why, including a useful amount and timing where the present knowledge supports them. A valid result can be that existing resources suffice or that quantification remains open.
Understand the intended capability, milestone or continuation, present assets, actual limiting relation and consequential time pressure. Do not derive the project need from a grant ceiling, provider bundle or familiar budget. A resource may be required to change a condition, preserve an operation or enable a new possibility. Keep distinct resultants separate when combining them would silently subsidize an unrelated objective through the same narrative.
Explain which resource changes which condition and makes which operation or result possible. Use that relation to understand the need, without requiring a form for every task. 'To grow' or 'for marketing' is insufficient when it does not identify the actual limiting relation. A cash need differs from valuation, expertise from headcount and distribution from a chosen platform. An eligibility condition may enable access without being the resource ultimately needed.
Distinguish an external resource gap from an asset not reached, a missing competence that can be formed, an unnecessary process demand or a real external dependency. Reuse and compose before assuming procurement. Computing capacity can be supplied by hardware, credits, infrastructure partnership, reduced cost or a changed architecture. Resource families can include data, evidence, attention, coordination, focused time, physical equipment or another function exposed by the work. Their current names do not close the field.
Where material, distinguish the continuity floor, transition runway and longer transformation horizon. The continuity floor has causal priority when its failure ends the work before later possibilities can exist; it does not become the whole purpose. A transition can use a bounded product, service, partnership or adoption milestone while preserving the wider direction. If an external return relation is needed, form an inspectable intermediate value bridge without making a capital provider the authority over the project's deeper purpose.
Identify minimum, sufficient amount, timing, duration and recurrence when knowable. An amount may be exact, bounded, scenario-dependent or unknown. Compare useful marginal capacity rather than maximizing the resource. When money is a useful translation, connect resource units, duration, unit cost and causally justified contingency. Keep that cash equivalent distinct from the function and from in-kind support; credits or contributed time are not money raised. Preserve the unknown that prevents responsible quantification.
Reach product architecture when delivery changes demand; research when current outside facts determine availability; funding expertise when the established need requires a financial route; qualified legal, accounting or other domain expertise when its actual mechanics matter. Expression follows the formed need. Acquisition, refusal, substitution or an unnecessary resource can change this method through their effect on the intended result. Successful fundraising alone does not prove the need was well formed. Stop when another pass changes no useful relation.
Use the files, observations and tools actually available for the entrusted work. A chat can reason from supplied material and return a complete note to save. A host with files can keep the competence and project guide reachable. Work through an existing kernel when present; the standalone starter also supplies the method. Ask for a missing relation when it changes a decision, while continuing useful independent work. Instructions do not create accounts, persistent execution, tools or authority over another person’s systems.
Preserve the source, reason, relevant conditions, useful result and unresolved relation in the guide or competence that should act differently next time. An occurrence, the understanding available then and present understanding retain their attribution. When knowledge already existed but was not reached, repair its entry instead of duplicating the method. Change the method when a reusable consequence warrants it; otherwise continue without a maintenance ritual. A written correction makes knowledge available. Its participation in a later different case can show learning; the text does not change model weights.
Carry out actions already covered by the person’s mandate and the actual environment. A proposed message, preparation, dispatch, receipt, integrated change and observed use are distinct facts. Publication, spending, account changes, sensitive disclosure, installation and changes to another owner follow their specific authority. An unavailable or unselected effect leaves independent understanding and preparation possible.
Read OPERATING_GUIDE.md and EXAMPLES.md as part of this method. They carry decision knowledge and worked cases. START_CHAT_EN.txt includes all three bodies for a chat without access to these files.
The direct work forms a resource function and its reason. A meta relation appears when it exposes a missing competence or a composition that changes the resource demand itself.
The method becomes its own object when the acquired resource fails to change the expected condition, or an unexpected substitute works. The reusable correction changes how later needs are recognized and quantified.
Competence, meta and autology: the conceptual guide ↗Compare the expected enabling relation with the actual consequence, retaining timing and conditions.
A resource may prove unnecessary, recurring rather than one-off, or sufficient at a different scale. Preserve the reason that changes the next decision.
Copy or attach START_CHAT_EN.txt and add your intent, relevant sources and available means. Save the useful continuation for the next session.
Make the complete folder reachable, start from SKILL.md and keep operating knowledge and examples beside it. The host determines actual tools, memory and actions.
Connect the method to the competence and project guides that already own the work. Preserve useful local knowledge when considering an update.
Read or copy the complete English starter and add your context. English is the kit’s primary language; Italian counterparts are included.
