Christ Rules

Introduction

Systematizing Systematic Theonomy: Presuppositional Sola Scriptura

Martin’s concern is valid, and it identifies exactly where the system could go wrong.

The dangerous failure mode is this:

The algorithm treats “creation order” or “covenant law” as if they are self-interpreting, when in fact fallen men are always interpreting them.

So the system must not say:

God by Scripture
God by creation order
God by covenant law

as though those three are equal, independent, automatically harmonious data streams.

It should say:

1. God speaks normatively and infallibly in Scripture.
2. Creation order is real, but must be interpreted by Scripture.
3. Covenant law is real, but must be interpreted by Scripture.
4. Theological writers are witnesses, never final arbiters.
5. The system must preserve disputed claims instead of silently harmonizing them.

Rushdoony’s own “Direction of the Law” lecture helps here: he insists that law comes from God, not man or the state, and that case law illustrates God’s principles rather than replacing them. He also warns that if man defines property, man can redefine or abolish it; Biblical law instead grounds property in God’s ordination. That same logic applies to definitions: if man defines “creation order,” man can redefine it.

Here is the algorithm I would add.

The Definition Source Arbitration Algorithm

1. Every definition claim must be stored as a claim, not as a conclusion

Never let the system ingest a definition as simply “the truth.”

Store it like this:

{
  "claim_id": "DEFCLAIM.MARRIAGE.0001",
  "term": "marriage",
  "proposed_definition": "Marriage is a covenantal union of male and female.",
  "claim_type": "definition",
  "source_basis": [
    "SCRIPTURE_EXPLICIT",
    "SCRIPTURE_NECESSARY_INFERENCE",
    "CREATION_ORDER_INTERPRETED_BY_SCRIPTURE"
  ],
  "scripture_refs": ["Genesis 2:24", "Matthew 19:4-6", "Ephesians 5:22-33"],
  "author_witnesses": ["Rushdoony", "Calvin", "Lightfoot"],
  "confidence": "high",
  "normativity_status": "candidate_normative",
  "review_status": "pending_human_review",
  "conflicts": [],
  "notes": "Creation-order claim must be controlled by Christ's appeal to Genesis, not by autonomous natural-law reasoning."
}

The key is candidate_normative.

Nothing becomes fully normative just because a theologian, tradition, or model says so.

2. Establish a strict source hierarchy

The source hierarchy should be:

S0 — Scripture: explicit statement
S1 — Scripture: necessary implication
S2 — Scripture: canonical pattern / repeated case-law principle
S3 — Creation order as interpreted by Scripture
S4 — Covenant administration as interpreted by Scripture
S5 — Confessional or theological witness
S6 — Historical lexical evidence
S7 — Natural observation / empirical data
S8 — Modern legal, social, or academic claims

This means:

Creation order and covenant law are real, but they are not autonomous interpretive authorities.

They must be brought under the rule of Scripture.

So the system should never allow this:

Creation order appears to say X.
Therefore Scripture must mean X.

It should require this:

Scripture teaches X.
Creation order may illustrate, confirm, or display X.

3. Add an Isaiah 8:20 gate

Every definition claim must pass the Isaiah 8:20 test:

To the law and to the testimony:
if they speak not according to this word,
it is because there is no light in them.

Algorithmically:

function isaiah_8_20_gate(claim):
    if claim.contradicts_explicit_scripture:
        return REJECT

    if claim.overrides_scripture_with_creation_order:
        return REJECT

    if claim.overrides_scripture_with_theological_system:
        return REJECT

    if claim.has_no_scriptural_anchor and claims_normative_authority:
        return DOWNGRADE_TO_DESCRIPTIVE_OR_DISPUTED

    return CONTINUE_REVIEW

This prevents “creation order” from becoming a theological blank check.

4. Add a “derivative truth cannot overrule source truth” rule

Martin’s Augustine example is excellent. Total depravity is true, but it is a derivative doctrinal truth. It cannot be used to limit God’s omnipotence.

So add this rule:

RULE.INTERPRETATION.NO_DERIVATIVE_OVER_SOURCE

Plain form:

No derivative doctrine may be used to deny, limit, or correct the source doctrine from which it depends.

Examples:

Total depravity may not overrule divine omnipotence.

Creation order may not overrule explicit Scripture.

Covenant administration may not overrule God’s immutable character.

Historical tradition may not overrule the law and testimony.

Natural observation may not overrule God’s revealed definition of man.

This is a crucial safeguard.

5. Require “warrant class” for every definition

Every definition should be assigned a warrant class.

WARRANT.EXPLICIT_TEXT
WARRANT.NECESSARY_INFERENCE
WARRANT.CANONICAL_PATTERN
WARRANT.APOSTOLIC_APPLICATION
WARRANT.CASE_LAW_EXTENSION
WARRANT.CREATION_ORDER_SCRIPTURALLY_INTERPRETED
WARRANT.COVENANTAL_ADMINISTRATION
WARRANT.CONFESSIONAL_WITNESS
WARRANT.THEOLOGICAL_OPINION
WARRANT.HISTORICAL_LEXICAL
WARRANT.NATURAL_OBSERVATION
WARRANT.MODERN_CLAIM

Then assign status:

NORMATIVE
STRONGLY_SUPPORTED
PROVISIONAL
DISPUTED
DESCRIPTIVE_ONLY
REJECTED

Example:

{
  "term": "unborn child",
  "definition": "A human child in the womb.",
  "warrant_class": [
    "EXPLICIT_TEXT",
    "CANONICAL_PATTERN",
    "CASE_LAW_EXTENSION"
  ],
  "status": "NORMATIVE",
  "definition_attacks": [
    "tissue_only",
    "potential_person",
    "maternal_property"
  ]
}

Example for a weaker creation-order claim:

{
  "term": "head covering in 1 Corinthians 11",
  "definition": "A required symbol of created hierarchy in all cultures.",
  "warrant_class": [
    "CREATION_ORDER_SCRIPTURALLY_INTERPRETED",
    "THEOLOGICAL_OPINION"
  ],
  "status": "DISPUTED",
  "requires_human_review": true,
  "notes": "Do not promote to normative without adjudicating competing exegesis."
}

That directly addresses Martin’s concern.

6. Do not erase conflicts — preserve them

This is very important.

The system must not force harmony prematurely.

Instead, it should preserve conflict as structured data:

{
  "conflict_id": "CONFLICT.1COR11.CREATION_ORDER.0001",
  "issue": "Meaning of creation order in 1 Corinthians 11",
  "claim_a": "Paul appeals to a permanent creation hierarchy requiring head coverings.",
  "claim_b": "Paul uses creation-order reasoning in a culturally specific honor-shame context.",
  "scripture_refs": ["1 Corinthians 11:2-16", "Genesis 2"],
  "status": "open_dispute",
  "adjudication_required": true,
  "cannot_use_for_normative_rule": true
}

So instead of the algorithm saying:

“Creation order proves X.”

It says:

“There are competing claims about how Scripture uses creation order here. This cannot be used as a settled normative definition until adjudicated.”

That is the antidote to GIGO.

7. Add a “normativity lock”

No claim becomes normative until it passes a stricter review.

function promote_to_normative(claim):
    if not claim.has_scriptural_anchor:
        return DENY

    if claim.conflicts_with_explicit_scripture:
        return DENY

    if claim.depends_on_creation_order_without_scriptural_interpretation:
        return DENY

    if claim.has_unresolved_major_conflict:
        return DENY

    if claim.uses_derivative_truth_against_source_truth:
        return DENY

    if claim.review_status != "approved":
        return DENY

    return APPROVE_NORMATIVE

This means the system may store, compare, and discuss many claims, but it cannot use them as authoritative until they pass review.

8. Add “definition authority” levels

Each term should include who has authority to define it.

AUTHORITY.GOD_BY_SCRIPTURE
AUTHORITY.GOD_BY_CREATION_INTERPRETED_BY_SCRIPTURE
AUTHORITY.GOD_BY_COVENANT_LAW_INTERPRETED_BY_SCRIPTURE
AUTHORITY.LAWFUL_OFFICE_MINISTERIALLY
AUTHORITY.HUMAN_CONVENTION_LIMITED
AUTHORITY.USURPED_FALSE_AUTHORITY

Example:

Personhood:
AUTHORITY.GOD_BY_SCRIPTURE
Not civil state, court, mother, physician, or academy.

Marriage:
AUTHORITY.GOD_BY_SCRIPTURE
Family, church, and civil order may recognize it ministerially, but may not redefine it.

Accused/convicted:
AUTHORITY.LAWFUL_OFFICE_MINISTERIALLY
A court may change procedural status, but not ontological personhood.

Property:
AUTHORITY.GOD_BY_SCRIPTURE
Civil law may adjudicate title, but may not abolish stewardship.

This distinction is vital:

A court can determine whether a man has been convicted.
It cannot determine whether he is a person.

9. Add “interpretive humility” flags

For hard areas, the system should not pretend certainty.

Use flags:

CERTAINTY.DOGMATIC
CERTAINTY.STRONG
CERTAINTY.PROBABLE
CERTAINTY.DISPUTED
CERTAINTY.SPECULATIVE
CERTAINTY.REJECTED

Then add:

CAN_SUPPORT_RULE = true/false
CAN_SUPPORT_APPLICATION = true/false
CAN_BE_USED_FOR_SEARCH = true/false
CAN_BE_USED_FOR_TEACHING = true/false
REQUIRES_HUMAN_REVIEW = true/false

A disputed claim can still be searchable and teachable, but not law-generating.

Example:

{
  "claim": "This creation-order pattern establishes a permanent civil rule.",
  "certainty": "DISPUTED",
  "can_support_rule": false,
  "can_be_used_for_teaching": true,
  "requires_human_review": true
}

10. Add the “no silent backfill” rule

Martin’s phrase about ambiguity being backfilled is exactly right.

So create:

RULE.INTERPRETATION.NO_SILENT_BACKFILL

Plain form:

If Scripture is ambiguous on a point, the system may not silently fill the gap with creation order, covenant law, tradition, or author preference. It must mark the inference and expose the warrant.

Algorithm:

if scripture_warrant == AMBIGUOUS:
    if claim_uses_creation_order:
        mark_as "CREATION_ORDER_INFERENCE"
        require_scriptural_control_texts
        require_conflict_scan
        require_human_review
    else:
        mark_as "UNRESOLVED"

This is one of the most important protections.

11. Add adversarial testing

Every proposed definition should be attacked before admission.

Ask:

1. What word is being defined?
2. Who is claiming authority to define it?
3. Is the claim explicit Scripture, inference, creation-order reasoning, covenantal reasoning, or theological construction?
4. Could this claim be used to override clearer Scripture?
5. Could this claim be a programmer/theologian bias disguised as creation order?
6. Are there faithful opposing interpretations?
7. Has the system preserved those opposing claims?
8. What happens if this definition is wrong?
9. What duties, protections, or sanctions would it create?
10. What duties, protections, or sanctions would it erase?

That last pair is essential.

A definition is dangerous when it erases a Biblical duty.

12. Add “harm of misclassification” scoring

Some definitions are high-risk.

RISK.LOW
RISK.MODERATE
RISK.HIGH
RISK.CRITICAL

Critical terms:

God
Christ
Scripture
Man
Person
Image of God
Male
Female
Marriage
Child
Unborn child
Murder
Theft
Justice
Church
State
Family
Authority
Covenant
Salvation

For critical terms, require a higher proof threshold.

if term.risk == CRITICAL:
    require EXPLICIT_TEXT or NECESSARY_INFERENCE
    require human_review
    require conflict_report
    prohibit autonomous_creation_order_basis

13. Add human review, but make it auditable

Martin asks, “Who will vet this?”

Answer:

The system should not hide the vetting process. It should expose it.

Every approved definition should show:

Approved by:
Date:
Scriptural warrant:
Opposing claims reviewed:
Reason for rejection/admission:
Confidence level:
Revision history:

Database table:

definition_reviews

id
definition_claim_id
reviewer_name
review_status
scriptural_warrant_summary
opposing_claims_considered
reason_for_decision
confidence_level
approved_for_normative_use
created_at
updated_at

That makes the system accountable.

14. The practical decision tree

Here is the usable form:

Definition Claim Enters System
        ↓
Is it explicitly taught by Scripture?
        ↓ yes
Check canonical harmony → approve or flag conflict
        ↓ no
Is it a necessary implication of Scripture?
        ↓ yes
Mark as strong, require review
        ↓ no
Is it a creation-order claim?
        ↓ yes
Require Scripture to interpret creation order
        ↓
Is it disputed among faithful interpreters?
        ↓ yes
Store as disputed; do not use normatively
        ↓ no
Mark provisional; require review
        ↓
Is it merely theological/traditional/natural observation?
        ↓
Store as witness, not authority

Shorter:

Scripture rules.
Creation witnesses.
Covenant administers.
Theologians testify.
The system records.
Reviewers adjudicate.
No disputed inference becomes law.

15. Revised foundational statement

I would change the earlier language from:

God by Scripture
God by creation order
God by covenant law

to this:

God defines all reality.

He defines infallibly and normatively by Scripture.

Creation order is real revelation, but because men are fallen interpreters, creation-order claims must be governed by Scripture.

Covenant law is real, but covenantal claims must be governed by Scripture.

Theological tradition, lexical history, natural observation, and scholarly argument may serve as witnesses, but never as autonomous sources of normativity.

That should satisfy Martin’s main concern.

16. Compact algorithm name

Call this layer:

Scriptural Supremacy and Definition Integrity Protocol

Or shorter:

Definition Integrity Protocol

Its governing rules:

1. Scripture is supreme.
2. Derivative truths cannot overrule source truths.
3. Creation order is interpreted, not self-interpreting.
4. Covenant law is administered, not autonomous.
5. Disputed claims remain visible.
6. No silent harmonization.
7. No normative promotion without warrant.
8. No definition may erase a duty God imposes.
9. No human office may redefine what only God defines.
10. Every approved definition must be auditable.

17. Strong answer to Martin

I would answer him this way:

Martin, your concern is exactly right. The system must not treat “creation order” or “covenant law” as equal independent sources beside Scripture. They are real, but they are interpreted realities, and fallen men can misread them. Therefore, the algorithm must make Scripture the only final and infallible norm, treat creation-order and covenant-law claims as subordinate witnesses, expose all warrants, preserve disputed interpretations, and prohibit any definition from becoming normative unless it passes a Scriptural supremacy review. The system should not eliminate perspective; that would be impossible. It should make the perspective explicit, auditable, corrigible, and subordinate to the law and testimony.

That is the key.

The system will not be protected by pretending to be neutral.

It will be protected by making its non-neutrality explicit:

God is true, every man a liar; therefore every human interpretation must remain reviewable under Scripture.

Comments are closed.