Raised method
Softpowers established the task as the base and method as a smaller, raised operator. Servotab preserves that hierarchy, day-first clarity, evidence-scoped claims, and proportionate depth.
03 / Lineage
Softpowers found the exponent. Servotab found how it applies force.
Servotab keeps the strongest construction insight from Softpowers while giving the public product its own mechanism, name, domain, and visual world.
The task stays the base. Method remains raised and conditional.
Exponent, not machinery
Method modifies the work without replacing it. The user’s task, repository, permissions, and requested outcome remain authoritative.
Controlled leverage
The raised p becomes a raised t: both notation and a real tab—attached, directional, bounded, and able to change a larger trajectory before settling.
Independent lineage
Shared problem domains. Independently written methods.
The project began as an independent rewrite inspired by obra/superpowers. It works across familiar engineering domains while independently defining its activation model, progressive disclosure, workflow thresholds, testing policy, review shape, delegation contract, and verification scope.
Additional method references and retained terminology are recorded in the repository’s Third-Party Notices. The License History preserves the forward-only licensing boundary across earlier revisions.
Retired identity
The lineage stays visible. The product moves forward.
Servotab is not presented as a lighter “power-up,” a cockpit, or a fixed workflow system. The exponent survives because it still explains the relationship between task and method; the new tab explains how that small method acts with bounded force.