A reference library of system logic concerned with building stability under constraint

Kindlearth exists to address a recurring failure in rural development and construction work: systems that fragment, lose authority, or decay once projects and funding cycles end. It maintains canonical system logic as a stewarded reference — defined by intent, boundaries, and constraints — so that knowledge remains coherent, inspectable, and viable over long horizons, particularly in resource-constrained and climatically exposed contexts.

Pre-Grant Coherence Check

A decision aid to identify system misclassification risk before funding is committed.

Purpose

The Pre-Grant Coherence Check helps decision-makers determine whether a proposal is being advanced under a system class whose assumptions are likely to hold in the stated context.

It operates upstream of feasibility, costing, and design. Its role is to prevent irreversible commitments to the wrong class of system.

What this check does

What this check does not do

Who this is for

This check is not intended for implementers seeking operational guidance.

How to use it

Negative outcomes are common and expected. Their value increases as constraints tighten.

Outcomes

The check returns one of three outcomes, each presented in two layers:

An outcome does not constitute approval or rejection. It clarifies whether a proposal should proceed under its current system framing.

✅ Outcome: Coherent

Layer 1 — Decision Summary (read this first)

This proposal is internally consistent with the conditions of the stated context. The system being proposed matches the constraints it depends on, and its key assumptions are realistic given expected variability in climate, materials, human capacity, and institutional support.

This does not mean the project is low-risk or guaranteed to succeed. It means the proposal is being advanced under a system class whose assumptions are explicit, plausible, and bounded.

From a funding perspective, this outcome indicates that the proposal may proceed to further consideration without correction at the level of system classification.

Layer 2 — Technical Rationale (reference)

The inferred system class is explicitly stated or can be clearly derived from the proposal. Governing Future Constraints are recognised and treated as binding rather than assumed away.

Preconditions and limits are identifiable. Failure modes are non-cascading and consistent with the stated system class. Assumptions required for coherence are compatible with projected future conditions.

Decision relevance: A coherent outcome does not constitute endorsement or approval. It indicates classification alignment only.

⚠️ Outcome: Coherent but Conditional

Layer 1 — Decision Summary (read this first)

This proposal is broadly consistent with the conditions of the stated context, provided specific conditions continue to hold.

The system class is appropriate, but coherence depends on limited continuities—such as institutional participation or material availability—that may weaken over time. If those conditions fail, the system degrades rather than collapsing, but continuity cannot be assumed.

From a funding perspective, this proposal may proceed only with explicit awareness of what must remain true and recognition that these conditions may not persist.

Layer 2 — Technical Rationale (reference)

The inferred system class remains valid within bounds, but relies on dependencies that are acknowledged yet not fully governed as binary preconditions.

Future Constraints are partially buffered but not fully internalised. Validity boundaries are conditional rather than firm, and coherence depends on continued availability of specified supports.

Decision relevance: A conditional outcome requires active recognition of dependency risk. If conditions cannot be reasonably expected or monitored, the proposal should not proceed under the current system framing.

❌ Outcome: Misclassified

Layer 1 — Decision Summary (read this first)

This proposal depends on several conditions continuing at the same time: materials remaining available, trained people staying in place, institutions continuing to function, and climate impacts staying within manageable limits.

In the stated context, those conditions are unlikely to remain stable together over time. Projects like this often appear successful during delivery and early reporting, but fail later—after funding ends—when the conditions they relied on weaken or disappear.

This check flags that risk before funding is committed. It does not judge intent or execution quality. It indicates that approving the proposal would rely on assumptions that are not stable.

Layer 2 — Technical Rationale (reference)

The proposal implicitly assumes a compound system class that requires multiple forms of long-term continuity. Governing Future Constraints in the stated context make those continuities unreliable.

Assumptions are not declared as explicit preconditions, thresholds, or failure conditions, leaving the system without a defined validity boundary.

Decision relevance: A misclassified outcome means the proposal should not proceed under its current system class. Proceeding without classification is itself a decision that assumes continuity by default.

Outcomes clarify system–context fit. They do not predict performance, assess delivery quality, or recommend alternatives.

Why this matters

Under tightening ecological, material, and institutional constraints, many projects fail after funding ends— not because they were poorly delivered, but because they were approved under assumptions that did not hold.

Proceeding without classification is itself a decision. It assumes continuity by default.

The Pre-Grant Coherence Check exists to make that assumption visible.

This tool is written for decision-makers. Technical system logic is available where needed, but decisions should not require fluency in the framework.

Worked Example

This example is fictional. It is published to illustrate how the Pre-Grant Coherence Check is used in practice.

Step 1 — Proposal snapshot

Proposal title: Climate-Resilient Community Housing and Livelihoods Programme

Applicant: International NGO

Context: Multiple rural districts across two countries

Duration / scale: 4 years · USD 6.5m · 3,000 households

Stated intent: Improve rural resilience by combining housing upgrades, livelihood support, and community capacity building.

Step 2 — What system is being assumed?

Although not explicitly stated, the proposal assumes an integrated rural settlement upgrade system, combining construction systems, household livelihoods, institutional coordination, and long-term material and skill continuity.

This system class requires multiple forms of continuity to hold at the same time.

Step 3 — Governing constraints in context

From the Future Constraints reference layer, the following are binding: climate variability, water instability, material availability limits, human capacity attrition, and institutional fragility.

The proposal acknowledges these descriptively but does not treat them as limits on system design.

Step 4 — Coherence outcome

❌ Outcome: Misclassified

Decision summary:

The proposal depends on several conditions remaining stable together over time: materials, skills, institutions, and climate impacts. In the stated context, those conditions are unlikely to hold simultaneously.

Projects of this type often perform well during delivery and early reporting, but fail later—after funding ends— when the conditions they relied on weaken or disappear. This risk is structural rather than operational.

Technical rationale:

A compound system class requiring multiple long-term continuities is applied in a context where governing constraints make those continuities unreliable. Assumptions are implicit rather than bounded, leaving no clear validity boundary.

Step 5 — Decision implication

This outcome does not assess execution quality or intent. It indicates that the proposal should not proceed under its current system framing.

Funders may still choose to act, but doing so would require accepting assumptions that are unlikely to hold.

Why this example matters

The value of the Pre-Grant Coherence Check lies in surfacing this risk before funding is committed.