research-document

Competing Theory Challenge

Purpose

Test whether existing disciplines already explain the observations currently attributed to Framework Engineering.

What does it already explain? Structured choice, tradeoff analysis, evaluation, and decision quality.
What does Framework Engineering add, if anything? Possibly stronger artifact characterization and grammar-focused decomposition.
Could it fully replace Framework Engineering? Possibly for choice-heavy artifacts.
What experiment distinguishes them? Compare FE and decision-science methods on artifact characterization and redesign tasks, not just decision tasks.

What does it already explain? System boundary definition, decomposition, interfaces, constraints, and verification logic.
What does Framework Engineering add, if anything? Possibly a broader artifact-theory lens beyond engineered systems alone.
Could it fully replace Framework Engineering? Possibly for system-heavy artifacts and redesign tasks.
What experiment distinguishes them? Test whether FE predicts or improves non-system-centric knowledge artifacts better than systems engineering methods do.

What does it already explain? Representation structure, ontology, semantic organization, and reasoning formalization.
What does Framework Engineering add, if anything? Possibly a stronger bridge from artifact characterization to redesign.
Could it fully replace Framework Engineering? Possibly for representation-heavy artifacts.
What experiment distinguishes them? Compare blind artifact characterization and redesign performance on ambiguous knowledge artifacts.

What does it already explain? Structured workflows, process optimization, sequencing, and control design.
What does Framework Engineering add, if anything? Possibly better distinction between reasoning structure and execution structure.
Could it fully replace Framework Engineering? Possibly if FE adds only generic process scaffolding.
What experiment distinguishes them? Compare FE redesigns against matched process-engineering redesigns on traceability and complexity tradeoffs.

What does it already explain? Sequence, routing, coordination, and process representation.
What does Framework Engineering add, if anything? Possibly stronger reasoning-layer decomposition.
Could it fully replace Framework Engineering? Possibly for execution-heavy artifacts.
What experiment distinguishes them? Test coordination-heavy cases where FE claims a reasoning/coordination grammar distinction.

What does it already explain? Expert reasoning structure, decision demands, and knowledge decomposition.
What does Framework Engineering add, if anything? Possibly more reusable cross-artifact grammar hypotheses.
Could it fully replace Framework Engineering? Possibly for reasoning-heavy artifact extraction.
What experiment distinguishes them? Compare primitive extraction and reconstruction quality using FE versus CTA-derived methods.

What does it already explain? Design process structure, iteration, solution generation, and evaluation.
What does Framework Engineering add, if anything? Possibly more explicit traceability and artifact-type characterization.
Could it fully replace Framework Engineering? Possibly for innovation and redesign cases.
What experiment distinguishes them? Compare FE syntheses against design-theory-derived syntheses on novelty problems.

What does it already explain? Verification, control, improvement cycles, and failure analysis.
What does Framework Engineering add, if anything? Possibly broader applicability across non-quality artifacts.
Could it fully replace Framework Engineering? Possibly for validation-heavy and control-heavy frameworks.
What experiment distinguishes them? Compare FE and quality-engineering redesigns in traceability-sensitive contexts.

What does it already explain? Need capture, constraints, validation, traceability, and refinement.
What does Framework Engineering add, if anything? Possibly more theory about framework structure itself.
Could it fully replace Framework Engineering? Possibly for specification-heavy artifacts.
What experiment distinguishes them? Compare artifact characterization and redesign output on ambiguous requirement-like frameworks.

What does it already explain? Theory revision, competing explanations, falsification, and epistemic caution.
What does Framework Engineering add, if anything? Possibly a domain-specific applied research program for framework artifacts.
Could it fully replace Framework Engineering? No, but it may fully explain how FE should govern its claims.
What experiment distinguishes them? This is less an experimental replacement and more a control lens: evaluate whether FE theory management obeys standard philosophy-of-science expectations.