Skip to content

Show us the strongest objections

A framework worth examining should make its liabilities visible. The aim is to understand the strongest version of a criticism before responding.

Objections we take seriously

These are stated at the strength a thoughtful skeptic would give them, not as the weakest version of a disagreement. None is resolved here; each points to where the site intends to engage it.

  • Isn't this just motivated reasoning? A project built to defend a prior theological commitment invites the charge that evidence is being fitted to a predetermined conclusion. That risk applies to any framework working from a starting commitment, not to this one uniquely, but naming the risk does not discharge it. What this site owes in response is a working discipline of falsifiable claims and an honest open problems register, including results that count against a favored proposal and not only those that support it.
  • Why should an ancient text count as evidence about the physical world? Scripture is a theological and testimonial source. Treating its historical claims as bearing on questions usually settled by measurement and inference requires an argument, not just an assertion that it does. That argument belongs to foundations and Scripture; it is not assumed by simply invoking the text.
  • Doesn't this require rejecting the scientific consensus? Where a canonical programme diverges from the current majority position in geology, cosmology, or biology, that divergence is a real cost and deserves to be stated plainly, not minimized or hidden behind selective citation of dissent. Domain pages will state where and how far a proposal departs from consensus as they develop; see compare frameworks.
  • Can intellectual honesty function from inside a faith commitment? A reader with no stake in the outcome may look freer to follow evidence wherever it leads. But every reasoner starts from some set of commitments. The question this site has to answer is not whether it has starting commitments, but whether its reasoning stays answerable to evidence built on them, including evidence that counts against its own proposals. See foundations and the status labels below.
  • Doesn't deferring to a "canonical source" let this site avoid being pinned down? A summary layer that always points elsewhere for the real claim can look like it insulates itself from challenge. The programme repositories this site routes to are public, versioned, and open to the same scrutiny as any other research; this site's obligation is to represent their current status accurately and route a challenge to the source that owns it, not to shield a claim from correction. See research programmes.

Make an objection inspectable

State the target claim or page, your argument, primary evidence, and the conclusion you think follows. Explain what a satisfactory response would need to address.

Submit an objection on GitHub

Substantive programme objections require review in the repository that owns the claim. This site can explain and route a challenge; it cannot settle it by changing a public summary.

The public objection-response register is in preparation. Existing programme liabilities should be inspected at the canonical sources.