EF 128
Enable an agent to recognise the Junkers EF 128 aircraft proposal, assess the evidence for its design and development state, and decide which descriptions or comparisons are justified.
Bundle → Layer → Finding → Questions Filled
5 bundles · 9 layers · 12 findings · 24 questions
Designation and project boundary Establish which records belong to the Junkers EF 128 proposal.
Designation evidence
Connect EF 128 names to attributable project records.
Project name attribution
Record the exact designation and Junkers attribution used by each source without silently normalising uncertain prefixes.
- Which contemporary document explicitly connects the EF 128 designation to Junkers? provenance
- Which expanded or prefixed names are contemporary designations and which are later catalogue conventions? definition
Revision membership
Determine which proposed configurations remain part of the same registered thing.
Configuration family boundary
Associate claimed EF 128 revisions with explicit documents rather than creating separate registered things from later illustrations.
- Which dated proposals establish distinct EF 128 configurations? provenance
- Do claims of alternative crew arrangements or mission versions describe documented revisions, related projects or later speculation? boundary
Proposed aircraft configuration Capture the physical arrangement needed to recognise and interpret an EF 128 proposal.
Airframe and control layout
Establish wing, fuselage, stabilising surfaces and flight-control arrangements for each baseline.
Attributable geometry
Resolve the reported swept-wing, tailless configuration against original drawings before treating detailed geometry as settled.
- Which original drawing establishes EF 128 wing planform, vertical surfaces and the presence or absence of a separate horizontal tail? provenance
- What dimensions and sweep reference line belong to that drawing, and are they stated or inferred from scale? measurement
- How does the same baseline assign pitch, roll and yaw control? definition
Propulsion and occupied spaces
Relate the proposed engine installation to intake routing, crew space and equipment allocation.
Installation baseline
Keep proposed powerplant, crew complement and equipment arrangements attached to the configuration that specifies them.
- Which primary record confirms or corrects the reported HeS 011 engine selection for EF 128? provenance
- What intake, exhaust, cockpit and equipment arrangement is shown in that same configuration? definition
- Which equipment items were baseline provisions and which were optional proposals? boundary
Requirements and performance evidence Separate what EF 128 was intended to achieve from what its design evidence supports.
Mission and selection
Establish the requirement and procurement context to which an EF 128 proposal responded.
Requirement traceability
Attach intended role and selection claims to dated requirements or decisions.
- Which contemporary requirement identifies the intended EF 128 mission and evaluation criteria? provenance
- What evidence distinguishes submission, favourable evaluation, development authorisation and production approval? boundary
Conditional performance
Record speed, climb, range and ceiling claims with their calculation or test basis.
Performance claim status
Preserve the provenance, configuration and conditions of each figure rather than assigning the proposal an unconditional operating envelope.
- For each EF 128 performance figure, is the source a requirement, contemporary estimate, test result or later reconstruction? provenance
- What altitude, mass, thrust assumption and fuel load accompany the figure? measurement
- Which comparisons with other fighter proposals remain valid when evidence classes and conditions are matched? action
Realisation and representation Determine how far EF 128 progressed and what surviving objects or depictions can establish.
Development milestones
Assess evidence for design completion, fabrication, testing and project termination.
Physical realisation evidence
Evaluate each claimed construction or test milestone independently; an intended aircraft does not establish a completed airframe.
- Which contemporary records establish whether EF 128 test models, mock-ups or full-size airframe components were actually produced? provenance
- What is the latest securely documented project milestone, and what remains unknown after it? boundary
Depictions and agent use
Classify EF 128 images and exhibits before using them as historical evidence.
Representation authenticity
Require provenance for images and objects, and label reconstructed details separately from documented design content.
- Who created the EF 128 depiction or object, when, and from which project documents? provenance
- Which visible features are documented and which were supplied by a modeller or illustrator? boundary
- May the agent use this item for identification, dimensional inference or only an explicitly labelled illustration? action
Evidence and external alignment What the world already says about this thing, gathered so the model can be checked against it.
Reported evidence
Findings from the breadth pass, kept separate from the structural claims.
Check these first
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these check these first hold for the sense of EF 128 this model covers, and on what evidence? provenance
Identifiers and schemes
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these identifiers and schemes hold for the sense of EF 128 this model covers, and on what evidence? provenance
Real-world use
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these real-world use hold for the sense of EF 128 this model covers, and on what evidence? provenance
Neighbouring kinds and how to tell them apart
Recalled without web access and unsourced; every item is a lead to verify.
- Which of these neighbouring kinds and how to tell them apart hold for the sense of EF 128 this model covers, and on what evidence? provenance
Classifiers Filled
- Family
- Thing Registry
- Category
- Physical world and living systems
- Entry kind
- thing
- Plane
- PHY
- Domain
- PHY.OBJ
What it is Filled
The Junkers EF 128 was a German single-engine jet fighter design proposed near the end of the Second World War that remained an unbuilt project.
In scope
- EF 128 designation, Junkers attribution and documentary identity
- Dated configuration proposals and their relationship to the registered design
- Airframe, propulsion, crew and equipment arrangements as proposed
- Performance requirements and estimates with their assumptions
- Evidence distinguishing design work, test articles, mock-ups and completed aircraft
- Uncertainty and permissible uses of reconstructed EF 128 information
Out of scope
- Jet fighters as a general aircraft class
- Other Junkers projects or competing fighter designs
- The Junkers organisation and the wider procurement programme
- Engine and weapon designs except their proposed integration into EF 128
- Individual museum exhibits, replicas and model kits as physical objects
- Fictional operational histories and modern flight authorisation
Why it exists Filled
Enable an agent to recognise the Junkers EF 128 aircraft proposal, assess the evidence for its design and development state, and decide which descriptions or comparisons are justified.
Distinguishing features Filled
- Require an EF 128 designation and Junkers attribution supported by a document or traceable catalogue record; the number 128 alone is insufficient.
- Distinguish the proposed aircraft design from an operational aircraft type by recording evidence of development maturity separately from intended capability.
- Use an attributable configuration drawing to establish identity; a generic swept-wing jet silhouette is insufficient.
- Treat an exhibit, kit or rendering labelled EF 128 as a representation until its relationship to original project evidence is established.
What robots and AI may and may not do Filled
Must not
- Present models or speculative reconstructions as built or flown aircraft.
- Invent performance figures for an unbuilt design.
- Promote myths of secret wonder weapons as fact.
Only with a human decision
- Publishing claims that parts of the project were built.
May
- Describe this unbuilt jet fighter project from documents and drawings, citing sources.
- Distinguish documented design data from later reconstructions and models.
Moral aspects Filled
- Myths about late-war projects glamorize a criminal regime.
- Fabricated history spreads quickly among enthusiasts.
Who is affected
- Historians
- Model makers and enthusiasts
- Readers
Owners Filled
Steward
Nobody: it was never built; archives hold the design records.
Links to other meta-models Filled
parent
- Q782885 - registry parent class
What else AI and robots need to interact with it Filled
Identity and identifiers required Filled
- Vercy registry: vr.tr.ef-128
- Wikidata: Q324019 (https://www.wikidata.org/wiki/Q324019)
Direct properties required Filled
- Documented designation: EF 128; Junkers EF 128; other forms only with provenance
- Configuration baseline: Dated drawing, report or proposal identifying a specific revision
- Development maturity: Proposal; documented design work; test article; mock-up; completed airframe; flight-tested; unresolved
- Airframe geometry: Span and length in m; wing area in m²; sweep in degrees with reference line
- Proposed powerplant: Engine designation, revision, count and installation source; unresolved where undocumented
- Performance evidence: Requirement; contemporary calculation; ground-test result; flight-test result; later reconstruction; unknown
- Speed and altitude pair: km/h with altitude in m, atmospheric assumptions and configuration
- Representation relationship: Original drawing; contemporary test article; contemporary mock-up; later replica; kit; illustration; unresolved
Recognition required Filled
- Known only from drawings, wind tunnel models and later replicas.
- Swept-wing jet layout with air intakes on the fuselage sides in drawings.
Capabilities and actions required Filled
- Match an EF 128 reference to the registered design using designation and documentary provenance.
- Compare proposed configurations while preserving revision boundaries.
- Classify performance figures as requirements, estimates or measurements.
- Assess whether a pictured object represents the design or constitutes evidence of contemporary construction.
- Identify conflicting claims and request the primary document needed to resolve them.
- Prepare a qualified catalogue description that exposes unresolved development and configuration claims.
Hazards and failure modes required Filled
- Speculative reconstructions are mistaken for history.
- Myths about such projects feed historical misinformation.
Standards and interfaces not applicable Not applicable
Not applicable
Operational aircraft certification standards are not applicable to this unbuilt historical proposal as a documentary design.
Context of use required Filled
- This unbuilt jet fighter proposal is encountered in studies of late Second World War aircraft development.
- Its surviving design documentation supports historical comparison and reconstruction of proposed features, while providing no evidence of demonstrated flight performance.
Sources Filled
- Wikidata item Q324019: EF 128 - identity and sense of the item
- Wikipedia: Junkers EF 128 - general description of the item
Open questions
- Which accessible original Junkers drawings or contemporary reports establish a reliable EF 128 configuration baseline?
- What physical work was completed, particularly given differing claims about drawing-board status, wind-tunnel models and fuselage mock-ups?
- Which engine installation, control arrangement, crew complement and equipment provisions are documented rather than reconstructed?
- Which published dimensions and performance figures trace to contemporary calculations, and what assumptions accompanied them?
- What documentary evidence establishes procurement decisions, termination chronology and any claimed alternative mission versions?
Machine files
Provenance
thing registry research (pass 2) · unreviewed
Built from: models/things/publications/thing-q324019/spec.json