Six pull requests merged. Two fixed live production defects: a catch-up request that exceeded the venue's 350-candle cap and self-wedged — the gap grew daily, so it could never recover — and a discovery filter that hid admissible assets. Both were verified against real production data, not only tests. Four more closed review findings, including one where a change had removed the only test pinning the admission liquidity floor: the floor could have been cut 5× with a fully green suite.
+Direction
+Every reachable strategy configuration has been measured and none is viable at this venue's cost. That result reframes what keel is for — and the answer is the part that works.
+ +Nineteen deterministic rails, attestation-based screening that fails closed, and §65.4 qabd encoded as an executable check that halts entries. There is no other open, auditable Shariah screening engine for spot trading — most halal-investing tooling is a closed app asking you to trust its list.
+So keel is being positioned as an auditable Shariah compliance engine, with a reference agent attached. The agent demonstrates the engine; it was never the product.
+Contributors from different madhāhib will disagree about rulings — what counts as riba exposure, how a staking wrapper or a governance token should be classified. Ungoverned, that fragments a project faster than any technical dispute.
+The architecture answers it: keel does not issue rulings. Attestation is a human input that fails closed — the operator supplies sector, backing and yield with a source and an attributed name, and keel enforces that deterministically. Nothing is derived from price data. A Hanafi operator and a Shafi'i operator can both use it, because the ruling lives in the attestation, not the code.
+Roadmap
-pullback_continuation's trade count and dropped its gross profit factor from 0.92 to 0.77 — the strategy takes trades it was designed to decline.
+ #260Honour a rule's conditional entry price Phase 9
+ The executor discards the entry level a rule computed and routes a market order. Not cosmetic: it doubled pullback_continuation's trade count and dropped its gross profit factor from 0.92 to 0.77 — the strategy takes trades it was designed to decline.
Phase 9 — Execution & backtest fidelity is new, and it groups these with the two closed defects of the same class that once voided every performance figure in the project. That is the honest home for them: all four are divergences between what a rule computes, what the backtest models, and what the venue actually does.
+ +| Phase | Outcome | Issues |
|---|---|---|
| 6 — Licence & discoverability Blocking | The repo is public but legally all-rights-reserved: no licence, no description, no topics. Nobody may contribute, and nobody can find it. | 4 |
| 7 — Contributor readiness | README written for a stranger, the documentation standard stated explicitly, the toolchain floor resolved, and a real on-ramp of shallow issues. | 7 |
| 8 — Scholarly grounding & launch | The fiqh basis written down, a review path decided honestly, an Arabic entry point — then announce, never before. | 4 |
Two of these are not code and matter most: stating that keel enforces rulings rather than issuing them, and deciding the scholarly review path honestly — including the option of saying plainly that no scholarly review has occurred. In this domain an overstated claim is not a marketing problem; it destroys the only thing worth having.
+ +The launch itself is a gate, not a task: nothing is announced until every prior box is ticked. A project that attracts attention before it can absorb it dies of that attention, and there is one first impression with this audience.
-Every reachable configuration has now been measured and none is viable at this venue's cost. That leaves three honest directions, and they are not equivalent:
+The turnover-reduction literature — the most promising family — was chased to its primary source this week and closed: its best-evidenced technique has already been swept in our own grids and produced nothing.