R&D Tax Relief for Software

Define measurable acceptance criteria and a competent professional’s assessment of why the intended capability exceeds routine adaptation. Attach dated requirements and a baseline comparison. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We want to investigate a synchronisation method for structured records edited offline by multiple users. Specify the baseline performance and the proposed improvement using units, tolerances, operating conditions and an objective pass/fail criterion. Ask the technical lead to identify which parts of the work involve an unresolved capability rather than ordinary design, procurement or compliance. Retain the original specification and its approval date so later changes can be traced.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For the R&D aim, use this work to identify what the field had already achieved; specify a measurable capability not shown by the source, without assuming novelty. Source: https://hal.inria.fr/inria-00555588/document

Prepare a dated literature table: author, year, institution, method, demonstrated capability, limitation, and the exact gap relevant to this project. Cite the source directly: A comprehensive study of Convergent and Commutative Replicated Data Types (2011). For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We have seen that conflict-free replicated data types and operational transformation are established approaches to replicated editing; convergence alone is not new. For every cited paper, distinguish the authors' demonstrated results from their stated limitations; do not infer that a published limitation automatically applies to this project. Record the publication date relative to the project start, the relevant experimental conditions and the nearest comparable method. Ask a competent professional to explain the remaining gap and attach the actual source passages or stable identifiers.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For current knowledge, record the publication date, experimental context, tested conditions and documented limitations. Compare these directly with the fictional project rather than asserting a research gap without evidence. Source: https://hal.inria.fr/inria-00555588/document

Explain the advance in overall science or technology, identify the nearest published approaches, and document why a competent professional could not readily deduce the result. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We hope to achieve a method that preserves domain-specific record invariants while reconciling concurrent offline edits. Describe the intended improvement as a testable capability, not as novelty to the company, cost reduction or a commercial advantage. Compare the target with the strongest available published method and explain which technical inference could not readily be made. State the experimental evidence that would support or refute the proposed advance, and identify any limits on generalising the result.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For the proposed advance, explain how the targeted capability would go beyond the methods demonstrated in the cited work. Do not equate a different product design with an advance in the field. Source: https://hal.inria.fr/inria-00555588/document

For each uncertainty record the prior method, what was unknown, why established approaches were inadequate, a falsifiable test, and the competent professional’s explanation. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We are unsure whether independent edits can converge without violating cross-field business constraints. Express each uncertainty as a question that can be answered through investigation, with boundary conditions and observable outcomes. Separate uncertainty about scientific or technological feasibility from uncertainty about budget, schedule, customer acceptance or supplier availability. Record what a competent professional knew at the outset, the alternatives considered and the evidence needed to resolve each question.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For uncertainty, isolate the unresolved technical question and contrast it with the published method’s demonstrated operating range and limitations. Obtain a competent professional’s explanation. Source: https://hal.inria.fr/inria-00555588/document

Attach feasibility assessments and alternatives considered; distinguish routine configuration, commercial risk and scientific or technological uncertainty. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We began because existing text collaboration methods do not automatically enforce the proposed structured-record invariants. Reconstruct the decision to begin the investigation using dated feasibility notes, early calculations and the team's prior-knowledge review. Explain why straightforward application or adaptation of existing methods could not settle the issue. Identify the point where routine engineering ended and the experimental investigation began, and record the competent professional who made that judgement.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For the reason to undertake R&D, document why applying the published approach was not readily sufficient and which alternative approaches were considered before experimentation. Source: https://hal.inria.fr/inria-00555588/document

Map each step to an uncertainty, a test or model, an acceptance threshold, a dated record, and a decision to continue, revise or stop. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We plan to define invariants; build baseline CRDT implementation; simulate partitions; test concurrent edits and schema migrations. For each proposed activity, name the hypothesis, variables to change, controls to hold constant, measurement method and decision criterion. Preserve failed iterations as well as promising ones, with versioned models, protocols and test data. Distinguish planned steps from completed work; update the sequence when the project changes instead of rewriting the original plan retrospectively.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For the planned steps, use the publication’s method or evaluation measures as a technical comparator, while documenting the business’s own test plan, controls and acceptance criteria. Source: https://hal.inria.fr/inria-00555588/document

Separate engineering execution risks from unresolved scientific or technological questions; document the effect each may have on experimental validity. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We anticipate out-of-order messages, deleted references, long offline periods and conflict-resolution ambiguity. Rank the foreseen technical obstacles by their effect on interpreting experimental results, and describe a mitigation or diagnostic test for each. Distinguish predictable implementation problems from limitations of existing scientific or technological knowledge. Record assumptions, expected failure modes, equipment constraints and the observations that would indicate the underlying uncertainty remains unresolved.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For foreseeable difficulties, distinguish limitations described by the authors from risks specific to the business. Explain how each could affect the proposed capability. Source: https://hal.inria.fr/inria-00555588/document

Replace this scenario with actual dated records. State the original assumption, new evidence, design change, and whether a new uncertainty genuinely arose. If none occurred, say so. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We might need to change the design. Use a dated change log to connect each unexpected observation to the original hypothesis and the resulting technical decision. Include the version of the design or protocol affected, the alternative explanation considered and the follow-up test proposed. Do not invent a new uncertainty merely to strengthen a claim; explicitly record 'none identified' if the actual project produced no new technological question.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For changes or newly discovered uncertainties, use the publication only as background; date and substantiate every actual design change or unexpected finding with company records. Source: https://hal.inria.fr/inria-00555588/document

Do not claim success or failure without results. Supply raw measurements, controls, repeatability, acceptance criteria, deviations and a competent professional’s conclusion. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We expect the design to improve. For every uncertainty, state separately whether it was resolved, partly resolved or unresolved and identify the test evidence behind that status. Include negative findings, measurement error, sample size or repeatability where relevant, and any difference between simulated and observed behaviour. Do not convert a proposed target into a claimed achievement; have the competent professional sign off the interpretation of actual records.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For outcomes, do not infer success from the publication. Compare the company’s actual measured results with the literature baseline, identify unresolved questions and report negative results. Source: https://hal.inria.fr/inria-00555588/document

Confirm the actual patent/application number and filing date if any. If none, say “No patent application filed”; explain any relevant confidentiality or other IP protection without suggesting that IP proves R&D eligibility. For the offline collaborative structured records investigation, relate this specifically to the business's stated issue: We may protect any new intellectual property. Separate an invention disclosure, an internal confidentiality decision and an actual patent filing; they are not interchangeable. If a filing exists, verify the application identifier, jurisdiction, date and the precise technical subject covered. If there is no filing or protectable result, state that plainly. Keep IP decisions distinct from the assessment of scientific or technological uncertainty and qualifying expenditure.

Published baseline: A comprehensive study of convergent and commutative replicated data types (2011; INRIA, France / European academic collaborators) — establishes CRDT concepts and known replicated-data convergence methods. For intellectual property, use the literature to check existing public disclosures and potential prior art; do not imply that a patent application was filed or that patentability has been established. Source: https://hal.inria.fr/inria-00555588/document