Question
The specific question the person or team is investigating and why it matters.
04 / People & projects
The work is the proof.
The XTF Portfolio documents what people investigated, how they worked, what they learned and where the work is going next.
Profiles are being prepared.
Projects will appear here when project information, evidence and publication permissions have been confirmed.
XTF will not fill this space with invented sample teams, inflated claims or work presented beyond its actual stage.
Until verified profiles are ready, this page publishes the standard every project record is expected to follow.
01 / Portfolio principle
No finished stories before the work is finished.
A first experiment is described as a first experiment. A prototype is not presented as a deployed solution. Evidence, uncertainty and next steps belong in every project story.
Method
How the work was researched, built, tested and reviewed.
Evidence so far
What is known at the current stage—and what remains uncertain.
XTF’s role
The support connected to the project, described without exaggeration.
Limitations
Constraints, risks and questions the work has not yet resolved.
Next step
The realistic path after the current program or review point.
02 / Stage language
Use the right word for the stage.
Consistent stage labels help visitors understand what a project has actually achieved. They are descriptive, not a ranking of importance.
Problem framing
The context and central question are being defined. No technical response is assumed yet.
Investigation
The team is learning from sources, people, observations or existing systems.
Testing an assumption
A bounded test is being used to learn whether part of the approach is credible.
Making the question tangible
An early form is exposing assumptions, interactions or technical constraints.
Testing in context
A limited real-world test is described only when the conditions, permissions and evidence are verified.
Following a next path
The project is pursuing further research, development or collaboration through a confirmed route.
03 / Project record
Make progress legible.
Each profile uses the same evidence-focused structure so visitors can understand the work without relying on promotional language.
People & program
Published names where permission exists, program, focus area and current stage.
Problem & question
The situation the work responds to and the question it asks.
Method & output
Research, tests, prototype and available public materials.
What changed
How critique or evidence altered the work.
Known limits
What the project cannot yet claim and what risks remain.
Where next
The work’s next responsible route and the record’s last-updated date.
04 / Evidence language
Tell readers where a claim comes from.
A project page should make the source and strength of important claims easy to understand.
Project-reported
Information supplied by the person or team and identified as such.
Documented
Supported by a method record, prototype material, source or test artifact available for review.
Reviewed
Discussed through a stated XTF review process without implying independent validation.
Independently supported
Used only when an appropriate external source or verification can be cited clearly.
05 / Publication standard
Consent, context and correction.
Publication is part of the responsibility around the work, especially when young people, sensitive information or early findings are involved.
Publish with consent
Names, images, project details and participant information appear only through the relevant permission process.
Limit personal data
A public profile should include only information necessary to understand the work.
Preserve uncertainty
Editing should not remove the limits or conditions that make a finding understandable.
Show the update state
A visible last-updated date helps readers distinguish the current record from an earlier stage.
Revise the public record
Material should be updated when a verified error or material change is identified.
Keep history legible
Archived material should not be mistaken for a current program status or present-stage claim.
Layered record
Process, product, observation, impact claim.
Keep four layers separate so an early project cannot be narrated as a finished outcome. No funding totals, endorsements or unnamed legal entities are added here.
Process
What was framed, investigated, made, reviewed and documented — including stops.
Product
The artefact that exists now: note, dataset, prototype, critique, or decision record.
Observation
What changed in the work or in understanding, with source (project-reported, documented, reviewed).
Impact claim
Only what the current evidence can support. If no impact report exists, say that the layer is empty.
06 / Portfolio FAQ
An honest record is more useful than a crowded gallery.
These answers explain why project profiles appear only after the underlying information is ready.
Why are there no public profiles yet?
XTF is waiting until project information, evidence and publication permissions can be confirmed. Empty space is preferable to an invented portfolio.
Does a prototype count as a finished solution?
No. A prototype is an early form used to expose assumptions or test part of a question. Its limitations remain part of the record.
Will every XTF project be published?
Not automatically. Publication depends on the relevant program terms, evidence, consent and a project record suitable for public use.
Does XTF independently validate every claim?
No general claim of independent validation is made. Each profile should state whether information is project-reported, documented, reviewed or independently supported.
Can a project record change?
Yes. A last-updated date and correction process keep the public record aligned with verified changes.
How can I ask about a profile?
Contact hello@xtf.org and identify the project or portfolio question clearly.