Skip to content

Commit 8c1c3ff

Browse files
authored
Update and rename 2025-04-02-musings-open-integrity.md to 2025-04-02-open-integrity.md
1 parent 288d6b9 commit 8c1c3ff

File tree

1 file changed

+0
-4
lines changed

1 file changed

+0
-4
lines changed

_posts/2025-04-02-musings-open-integrity.md _posts/2025-04-02-open-integrity.md

-4
Original file line numberDiff line numberDiff line change
@@ -60,8 +60,6 @@ Solving Git's trust issues are relatively easy in theory:
6060
4. Strong warnings are needed when these conditions aren't met.
6161

6262
However, nothing is ever that simple in practice. To practically solve the problems required designing an Open Integrity architecture that resolved each of the highlighted problems:
63-
64-
<center>
6563

6664
| Problem | Solution |
6765
|---------|----------|
@@ -72,8 +70,6 @@ However, nothing is ever that simple in practice. To practically solve the probl
7270
| Merging Issues | Scripted Functions<br>Data Preservation<br>Defined Settings |
7371
| History Issues | Improved Logging<br>Defined Settings |
7472

75-
</center>
76-
7773
Here's how each of these architectural elements work:
7874

7975
***Inception Commit.*** An inception commit is the first commit made to a repo. It locks the repo's inception (initial) key with an empty commit, and so secures the repo with both the SSH signature and a SHA-1 hash that's hard to purposefully collide because of the minimalism of the commit.

0 commit comments

Comments
 (0)