FEATURE
Named, executable skills
Define repeatable product work with a name, instructions, inputs, outputs, evals, and connector requirements.
IMPACTA good workflow becomes reusable product infrastructure instead of a prompt someone has to remember.
f() / SYSTEM ITEM
Executable Product Knowledge
Productf functions give recurring product work a name, a contract, a context boundary, and a reviewable output so teams can build a system instead of collecting prompts.
WHAT IT TAKES IN
Context becomes useful when the inputs are named.
WHAT IT GIVES BACK
Outputs you can pick up and act on.
FEATURES
What f() changes in the way product work gets done.
This is the operating behavior behind the promise. Each capability is designed to make context, action, and accountability easier to see.
FEATURE
Skill-level evaluation
Measure quality against explicit criteria and test cases before a function becomes trusted.
IMPACTTeams improve the work itself, not only the model behind it.
FEATURE
Inspectable run traces
Expose Brain reads, connector calls, files, tool use, agent handoffs, and produced artifacts.
IMPACTAutomation becomes reviewable enough to operate in real product work.
FEATURE
Artifact-first outputs
Return a report, brief, decision, task set, or other durable output that can move into the next step.
IMPACTThe result is something the team can pick up, review, and act on.
PRODUCTF PROMISE
Automation should make judgment easier to see.
The workflow has a nameInputs and outputs stay explicitReuse compounds product knowledge