The article is well written, and is relevant to the topic it discusses.
The methodological proposal that is made is powerful from the point of view of archaeological study and concerning the durability of the data.
The topic is explained correctly, although due to the length of the text some specificity is missing in the type of technological solution adopted.
The proposal is important from the perspective of interoperability and the use of data from different platforms, although it is not explained how this would be done. We assume, again, that this is an extension issue.
In any case, this is a significant contribution and we believe it deserves to be published.

This preprint introduces HORAI as a "semantic-based integration model" to support and inform the other systems used by Historical Sciences scholars. The below review is informed by having read the Guide and Questionnaire for Reviewers, so it will point out some strengths, flaws, gaps, suggestions, and significances of the preprint, which seems to have been presented at the recent April 2023 CAA: Computer Applications...in Archaeology conference. The paper explores HORAI's premise of "integrated management processes" (line 118) that build on interoperability (achieved) between the systems and repositories used by a project team members. HORAI's model uses the three units of topography (UT), stratigraphy (US), and actor (Ac) and this paper connects the three to archival processes which do for archival arrangement what HORAI would do for archaeological interpretation - that is, for the latter-the work of an archaeologist. The first half of the paper provides a justification for HORAI in an archaeological environment comprised of "one or more disciplines" that needs its solution in "data modelling" (lines 72-3). Therefore the HORAI model aligns and "bridges our databases" (line 138) in a way that allows each to retain its disciplinary origins and contributions while allowing them to be in dialogue for the purposes of archaeological scholarship. I thought the second half (from Lucas on line 141) of the second section on "integration" got a little far from the stated focus on HORAI itself, but somewhat understandable given the later reiteration that this paper presents "the elements that help us understand the [processes and dynamics] within the context in which they are developed, not ... the technical aspects" (line 242). Still a suggested improvement would be to further organize or add subheadings to the conceptual Integration section. ----- The third section compares the ISAD-G (line 188) archival processes with those used in HORAI, which I found to be a helpful section with its orderly explanations of four adjacent "management phases" but there is room to be more explicit about their relationship with Figure 1. Does all of Figure 1 happen during phase 3 "data processing" e.g. which ISAD-G - which otherwise drops out entirely from the rest of the paper! - might suggest? Given the frequent mentions of Archival Science as an informative foundation for the development of HORAI and the "three tools" (line 235) further developed from HORAI, a current gap to be addressed would be more archival description-within Archival Science citations and detailing of them, so that the reader clearly sees where HORAI differs and adapts *from* *them* to attend to the needs of archaeology. That would further emphasize the comparison focus of the third section. ----- The fourth section reports on three tools / systems collaboratively and cross-institutionally developed to achieve research goals. They articulate the advancements HORAI makes to the shared goals of data "conceptual reconciliation and efficiency" (line 304) and "define traceability in our work with information" (line 310). ----- I'd like to see much more said about the next step aim of "decelerate methodological processes characterized by streamlining and simplification of information" (line 313) - this seems like a refreshingly honest pressure point that needs some grounding to make it be more than words. I like the idea that data modeling is a "simplification of information" that might tie well into information visualization efforts employed in a range of information and heritage institutions and even taught to information students, so there is room please to explain and make that outward connection in the fifth section: Discussion. Figure 2 is great, as are the footnotes linking to its website, concluding parts, and fresh references. The title does suggest a more "technical" (line 242) kind of paper that the authors immediately disabuse the reader is not what's here, so adding the word 'model' or 'modeling' to it, is a constructive suggestion. Do consider mentioning the Spain context of all this work in the abstract at least, as it gives coherence to some spots in the text. A well-written and accomplished paper.