Decisions log — SELIS V2
Newest entries at the bottom. Each entry: date, decision or fact,
reason or source. When an entry changes CLAUDE.md, update
that file too.
2026-11-13
Facts confirmed by Ivaylo
| # | Fact | Source |
|---|---|---|
| F1 | Applicant is Luminous Ltd, registered and approved on esa-star. | Ivaylo |
| F2 | SELIS stands for Site Environment & Landing Infrastructure Simulator. | Ivaylo |
| F3 | Official closing is 26 November 2026, 13:00 Amsterdam time (14:00 in Sofia). Ivaylo's working deadline is 25 November. | ESA cover letter point 13; Ivaylo |
| F4 | Type A constraints: start TRL at least 1, end TRL at most 3, 9 to 15 months, firm fixed price up to EUR 200,000, end-customer highly encouraged. The overall threshold for Type A is 55, not 50. | ESA cover letter points 4 and 7c |
| F5 | Evaluation weights are 40% technical and team, 30% prospects and maturity, 25% management, cost and planning, 5% administrative and IPR compliance. | call-docs/ESA - TA Information.txt |
| F6 | Current state is early feasibility only: Ames Stereo Pipeline set up locally and DEMs produced from stereo pairs, NASA DEMs and LROC PDS archive explored, Rhino Grasshopper PV-potential demos on generated DEMs. | Ivaylo |
| F7 | The RFI response was submitted; Bulgarian entities were not eligible; ESA replied that it is reviewing the project. | Ivaylo |
| F8 | Key personnel so far: Ivaylo Tsankov and Martin Ivanov. Martin's CV is pending. | Ivaylo |
| F9 | Only one potential customer so far: a Lithuanian micro company developing solar panels for space and the Moon, also applying to ESA. In negotiation. | Ivaylo |
| F10 | Proposal limit is 25 pages, excluding cover letter, PSS forms and annexes. Annexes are not marked. | ESA cover letter point 8c |
| F11 | AI use must be disclosed in cover letter point 9 (proposal elements) and section 2.4.3 (deliverables). | Tendering conditions 4.2; proposal template |
| F12 | The clarification-question window closed on 12 November 2026 (14 calendar days before closing). | ESA cover letter point 12 |
| F13 | Non-Bulgarian entities may take part only where justified, not for core work, with subcontracts at most 20% of the price. Lithuania has been an ESA Associate Member since 21 May 2021. | ESA cover letter point 2; ESA news release |
| F14 | Type A is fully funded; profit at most 8% of PSS A2 item 9. Procurement of infrastructure and generic tools is out of scope. | ESA cover letter points 4 and 6; proposal template 3.2.1 |
| F15 | TRL 3 means an analytical and experimental proof of concept of critical functions; TRL 4 is breadboard validation in a laboratory environment. ESA's Technical Officer verifies the TRL at the end. | Draft contract, Appendix 4 |
| F16 | At most 2 proposals as prime and 3 in total per entity under this call. | ESA cover letter point 9 |
| F17 | Duplication of ongoing or intended ESA activities leads to a programmatic down-mark and possible rejection. | ESA cover letter point 6 |
| F18 | Transfer of IP arising from the work to an entity outside Bulgaria needs prior authorisation of the Bulgarian government, requested through ESA. | Draft contract 6.5 |
| F19 | Luminous Ltd expressed interest in the call in esa-star on 13 November 2026. | Ivaylo |
| F20 | Luminous Ltd is registered as an SME in esa-star, so it is entitled to a 35% advance payment. | Ivaylo; proposal template 3.2.2 |
| F21 | README.md and AGENTS.md are symlinks to
CLAUDE.md, which is the master file. |
Ivaylo |
| F22 | ESA published nine clarifications (26 October to 12 November 2026). None changes the deadline, limits or criteria. | call-docs/clarifications/ |
| F23 | Cloud processing and similar activity-specific recurring costs are in principle eligible (PSS A2 items 3.1 to 3.7 or 3.10, plus Exhibit A). Infrastructure, including upgrades and depreciation, is not. | Clarifications 9.3 and 2.1 |
| F24 | Letters of interest from prospective users may be annexed and are considered in the evaluation. A subcontract with the end customer is encouraged but not required for Type A. | Clarification 9.6 |
| F25 | A subcontractor cannot be shown at zero cost; it needs its own PSS forms and may waive payment on PSS A2 line 14. | Clarifications 1.1 and 3.2 |
| F26 | The start TRL is assessed at the level of the system being developed, justified from component maturity and demonstrated integration. | Clarification 9.4 |
| F27 | A Type A proposal should substantiate the path beyond TRL 3: mission, end users, business case, state of the art. A named mission or user strengthens it but is not required. | Clarification 9.2 |
| F28 | Owner-manager labour may be budgeted for Type A if the person is actually paid by the company; rates are assessed by the TEB; no prior rate agreement is needed. Economic conditions year may be 2027. | Clarifications 5.6, 6.4 and 7.1 |
| F29 | ESA staff cannot act as advisers to a tenderer or endorse a proposal. | Clarification 6.5 |
| F30 | Background IP needed for the activity must be declared even if not delivered. No general open-source obligation. The contractor keeps commercial exploitation rights, subject to ESA's rights. | Clarifications 8.1 to 8.4 and 9.5 |
| F31 | Luminous Ltd is an EOOD. Ivaylo Tsankov is its sole owner and manager, is self-insured, is paid by the company, and is currently the only person paid by it. | Ivaylo |
| F32 | Martin Ivanov is not currently engaged by Luminous Ltd. He works hybrid and can do his SELIS work from Bulgaria. An employment or civil-law contract can be set up. | Ivaylo |
| F33 | PSS instructions: rates follow the company's normal accounting practice and are marked provisional or definitive; rates not agreed with ESA are subject to negotiation; ESA may audit. A supplier under item 3.7 (external services, including consultancies) cannot be responsible for a work package. | call-docs/PSSA1_i5.xlsx, PSSA2_i5.xlsx,
Instructions sheets |
Decisions
| # | Decision | Reason |
|---|---|---|
| D1 | Apply under Type A (Research and Preparatory Activities). | Matches the maturity of the idea and the current state (F6). |
| D2 | Luminous Ltd is the prime. No subcontractors, academic partners or advisers for now; add one only if critical to success. | Keep the consortium simple; revisit after scope is set. |
| D3 | IP towards ESA follows the ESA contract conditions; everything else is retained by Luminous Ltd. Intended future market: private companies, academia, possibly other agencies. | Ivaylo's position. |
| D4 | The call documents are kept as blank templates; nothing is carried over from the RFI draft automatically. | Clean slate, so the proposal is built for PECS, not adapted from the RFI. |
| D5 | Scope will be derived from the Type A definition, the guide, the budget and the timeline, and only then mapped onto the SELIS vision. | The full vision does not fit a Type A activity. |
| D6 | Feature research is allowed (topic E in
research-brief.md), with innovation permitted where
grounded in existing data, published methods and a credible verification
path; each feature gets an evidence grade and B and C features need a
fallback. |
An early-stage project benefits from exploring options, but the proposal must stay deliverable. |
| D7 | Working rule for all chats: call documents first, playbook second,
CLAUDE.md third; no invented facts; unknowns marked
[TBD]. |
Set in the project instructions. |
| D8 | Internal target: submittable proposal by 23 November, two days before the deadline. | Margin for forms, signatures and upload problems. |
| D9 | Proposal text follows a plain technical English rule set derived from ASD-STE100 (sentence and paragraph limits, active voice with named actor, one term per thing, no vague qualifiers). Full STE compliance is not claimed or attempted. | Clarity is part of the 40% criterion and evaluators may be non-native readers; full STE needs a licensed dictionary, suits manuals not proposals, and cannot be verified by the agents. |
| D10 | Glossary moved from CLAUDE.md to
glossary.md, which is the single source for terms. |
Keeps CLAUDE.md short and gives rule 5d one place to
check. |
| D11 | Sprint plan moved from CLAUDE.md to
sprint-plan.md, with a status column. |
Keeps CLAUDE.md short; the plan changes often and the
rules do not. |
| D12 | The Type A activity focuses on the lunar South Pole. The specific site or sites within it remain open. | Ivaylo's decision. Consistent with the feasibility work done so far and with the data sets already explored. |
| D13 | The production pipeline, data sets and tools described in
CLAUDE.md are a baseline hypothesis from the RFI draft, not
a fixed design. Research topics B and D must look for alternatives. |
Avoids research that only confirms the RFI design, and keeps the Type A scope open. |
| D14 | Guide and call package distilled into pecs-playbook.md,
compliance-matrix.md and evaluator-rubric.md.
Where guide and call differ, the call is followed; differences are
listed in playbook section 10. |
Order of authority (D7). |
| D15 | Working target for the evaluator rounds: 70 or more overall and no criterion under 55. | The threshold of 55 only makes a proposal eligible; proposals of all types share one budget and the national delegation selects from the ranking. |
| D16 | ESA clarifications 1 to 9 are treated as part of the call documents and incorporated into the playbook (section 11), the compliance matrix (block K) and the rubric. | They are official ESA answers. |
Open (to be decided)
| # | Question | Depends on |
|---|---|---|
| O1 | Type A scope and what is out of scope | Distillation, research |
| O2 | End goal and deliverables. Boundary now known (F15): proof of concept of critical functions for one site, not an integrated validated system. Which functions, and what proves each, is open. | Concept note |
| O3 | Start and end TRL with evidence | O1, O2 |
| O4 | Duration, price, work packages (fully funded is settled, F14) | O1 |
| O5 | Team roles and time shares; whether an AI specialist is needed | O1, research topic E |
| O6 | How the Lithuanian customer is involved. Both routes are accepted by ESA (F24): a letter of interest in an annex, or a subcontract in a customer role, which needs its esa-star registration, its own signed PSS forms with non-zero cost (F25) and CVs. | Negotiation; time left |
| O7 | Whether any partner or adviser is critical | O1 |
| O8 | Closed: see F3 and F16. | — |
| O9 | Which specific South Pole site or sites | Research topics B and C (data coverage, user interest) |
| O10 | AI disclosure text for the cover letter and section 2.4.3 | Written at the end, from what was actually done |
| O11 | Whether any existing Luminous work is declared as background IP | Scope |
| O12 | esa-star: check the entity data was updated in the last 12 months (cover letter point 4); decide whether to request the 35% advance; re-check the call page for new documents or clarifications before submission | Ivaylo |
| O13 | Partly closed: cloud processing for the activity is eligible in principle (F23). Still open: whether specific software licences count as activity-specific costs or as generic tools. | Costing |
| O14 | Remuneration arrangements for the activity: Ivaylo's rate as owner-manager, and Martin's engagement (employment or civil-law contract as direct labour, not an external service, if he manages a work package). ESA does not require these to be in place at submission; they must be lawful, described in the proposal, and actually applied during the contract. To be confirmed with the company's accountant. Also to check: Martin's university rules on outside work and IP. | Ivaylo, accountant, Martin |
| O15 | Start TRL to claim at system level (likely 1 or 2), with the evidence available today. | Concept note |
2026-11-14
Facts confirmed by Ivaylo
| # | Fact | Source |
|---|---|---|
| F34 | Bulgaria is a full EU Member State and has been in the euro area
since 1 January 2026. Luminous Ltd costs and quotes in euro; the
exchange rate on the PSS forms is 1. compliance-matrix.md
row G3 and pecs-playbook.md section 6 previously said
Bulgaria was outside the euro zone; both corrected. |
Ivaylo; Council Decision (EU) 2025/1407 of 8 July 2025, https://eur-lex.europa.eu/eli/dec/2025/1407/oj |
Decisions
| # | Decision | Reason |
|---|---|---|
| D17 | Product direction is fixed: software for mission planning for lunar
exploration, with a focus on the lunar South Pole. Everything else about
the product may be challenged in a grilling session, to find the idea
with the best unique proposition against competitors, feasibility with
available data, fit to customer needs and fit to Type A (TRL 1 to 3).
The session follows grilling-brief.md and produces
concept-note.md. For that session D17 overrides
CLAUDE.md section 2 and rule 10; CLAUDE.md is
updated only after the result is confirmed. |
Ivaylo's decision, 14 November 2026. The SELIS description comes from the RFI draft and was not designed for Type A. |