File size: 180,856 Bytes
40a7a1e 1476ff0 40cda58 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 893abe8 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 41252de 189d663 41252de 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 ea41c5d 1476ff0 6c0f56a 1476ff0 ea41c5d 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 ea41c5d 1476ff0 ea41c5d 1476ff0 ea41c5d 189d663 ea41c5d d67e5b8 ea41c5d e2adf1f 1476ff0 6c0f56a 1476ff0 ea41c5d 1476ff0 ea41c5d 1476ff0 6c0f56a 1476ff0 ea41c5d 1476ff0 ea41c5d 1476ff0 ea41c5d 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6eb4e3e 1754ecd 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 1754ecd 0a60d61 1754ecd 1476ff0 5dcd7a6 1476ff0 a686978 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 8813e66 5dcd7a6 1837e0d 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 5dcd7a6 1476ff0 f1b479d a686978 1476ff0 6865b8c 1476ff0 1754ecd 02d1952 1476ff0 10e1027 1476ff0 6c0f56a 1476ff0 6cf7a6e 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 0b0d8a7 1476ff0 2208755 1754ecd 02d1952 1754ecd 02d1952 2208755 1754ecd 2208755 1754ecd 02d1952 2208755 02d1952 1754ecd 02d1952 1754ecd 02d1952 a21cf90 8f79c75 02d1952 8f79c75 02d1952 1754ecd 02d1952 2208755 02d1952 8f79c75 02d1952 8f79c75 02d1952 8f79c75 02d1952 8f79c75 02d1952 8f79c75 02d1952 8f79c75 02d1952 8f79c75 02d1952 1754ecd 02d1952 1754ecd 02d1952 1476ff0 6865b8c 1476ff0 6865b8c 1476ff0 6865b8c 1476ff0 6865b8c 1476ff0 6865b8c 1476ff0 6865b8c 1476ff0 02d1952 1476ff0 02d1952 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 02d1952 1476ff0 02d1952 1476ff0 02d1952 1476ff0 02d1952 1476ff0 02d1952 1476ff0 02d1952 6eb4e3e 02d1952 6eb4e3e 02d1952 6eb4e3e 02d1952 6eb4e3e 02d1952 6eb4e3e 02d1952 6eb4e3e 1476ff0 a33dd5b 02d1952 1476ff0 a33dd5b 1476ff0 02d1952 1476ff0 a33dd5b 1476ff0 a33dd5b 1476ff0 a33dd5b 8813e66 a33dd5b 1476ff0 a33dd5b 1476ff0 02d1952 1476ff0 a33dd5b 8813e66 a33dd5b 8813e66 a33dd5b 02d1952 1476ff0 a33dd5b 67fc437 a33dd5b 1476ff0 a33dd5b 1476ff0 8813e66 1476ff0 a33dd5b 1476ff0 a33dd5b 1476ff0 a33dd5b 1476ff0 a33dd5b 1476ff0 02d1952 1476ff0 a33dd5b 1476ff0 a33dd5b 8813e66 a33dd5b 1476ff0 a33dd5b 02d1952 1476ff0 a33dd5b 1476ff0 02d1952 6865b8c b779f20 6865b8c b779f20 6865b8c b779f20 6865b8c b779f20 6865b8c b779f20 6865b8c 02d1952 1476ff0 02d1952 1476ff0 4b8cf53 1476ff0 02d1952 1476ff0 02d1952 1476ff0 697f38e 1476ff0 02d1952 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 ea41c5d 189d663 d67e5b8 ea41c5d 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 6c0f56a 1476ff0 8eb73af 6eb4e3e 8c039fd 6c0f56a 8c039fd beae091 8c039fd beae091 8c039fd beae091 4b8cf53 8813e66 893abe8 8c039fd beae091 8c039fd beae091 8c039fd beae091 8c039fd beae091 8c039fd 6c0f56a 8c039fd 2208755 8c039fd 6c0f56a 8c039fd 2208755 8c039fd 893abe8 8c039fd 2208755 8c039fd 893abe8 8c039fd 2208755 8c039fd 2208755 8c039fd 2208755 8c039fd 2208755 8c039fd beae091 8c039fd 2208755 8c039fd beae091 8c039fd beae091 8c039fd beae091 8c039fd beae091 8c039fd 4e02fe9 2208755 8c039fd 2208755 8c039fd 6c0f56a 8c039fd 2208755 8c039fd 6c0f56a 8c039fd 6c0f56a 8c039fd 4b8cf53 8c039fd 4b8cf53 8c039fd 6c0f56a 893abe8 8c039fd 893abe8 8c039fd 893abe8 8c039fd 893abe8 8c039fd 893abe8 8c039fd 893abe8 8c039fd 893abe8 8c039fd 2208755 8c039fd 6eb4e3e 6c0f56a 1476ff0 b779f20 1476ff0 d8159e6 1476ff0 d8159e6 b779f20 d8159e6 40a7a1e d8159e6 2208755 7da541a d8159e6 40a7a1e 7da541a 2208755 7da541a 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 5f85f92 2208755 7da541a d8159e6 40a7a1e d8159e6 2208755 a21cf90 115e3ba 2208755 115e3ba a21cf90 115e3ba 2208755 115e3ba 2208755 115e3ba a21cf90 2208755 a21cf90 115e3ba 2208755 a21cf90 2208755 a21cf90 2208755 115e3ba 40a7a1e 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba c1baf21 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba 2208755 115e3ba f5a80a1 115e3ba 97f909f f5a80a1 97f909f f5a80a1 97f909f 7da541a d8159e6 2208755 d8159e6 6c0f56a f5a80a1 d8159e6 6c0f56a d8159e6 f5a80a1 d8159e6 6c0f56a f5a80a1 d8159e6 f5a80a1 d8159e6 6c0f56a f5a80a1 d8159e6 f5a80a1 115e3ba d8159e6 2208755 d8159e6 f5a80a1 115e3ba d8159e6 115e3ba f5a80a1 115e3ba d8159e6 f5a80a1 115e3ba f5a80a1 d8159e6 2208755 d8159e6 f5a80a1 d8159e6 f5a80a1 d8159e6 f5a80a1 d8159e6 f5a80a1 1476ff0 b779f20 1476ff0 b779f20 1476ff0 6db912d 1476ff0 b779f20 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d b779f20 6db912d 1476ff0 6db912d 1476ff0 b779f20 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d 1476ff0 b779f20 6db912d 1476ff0 6db912d 1476ff0 6db912d f42c36c 6db912d 1476ff0 b779f20 1476ff0 6db912d 1476ff0 b779f20 1476ff0 6db912d 1476ff0 6db912d 1476ff0 6db912d 1476ff0 b779f20 1476ff0 6db912d ecd5b40 1476ff0 6db912d 1476ff0 6db912d 41252de 6db912d 41252de 6db912d 41252de 6db912d 1476ff0 b779f20 6db912d 1476ff0 6db912d 1476ff0 b779f20 cb914d0 b779f20 cb914d0 b779f20 cb914d0 b779f20 cb914d0 b779f20 cb914d0 b779f20 cb914d0 b779f20 cb914d0 b779f20 cb914d0 15c86d5 cb914d0 b779f20 cb914d0 15c86d5 cb914d0 b779f20 cb914d0 b779f20 cb914d0 1476ff0 b779f20 b8cf202 b779f20 b8cf202 b779f20 b8cf202 15c86d5 b8cf202 b779f20 b8cf202 b779f20 b8cf202 b779f20 b8cf202 b779f20 b8cf202 b779f20 b8cf202 15c86d5 b8cf202 15c86d5 b8cf202 b779f20 b8cf202 15c86d5 b8cf202 15c86d5 b8cf202 b779f20 b8cf202 15c86d5 b8cf202 b779f20 b8cf202 15c86d5 b8cf202 b779f20 b8cf202 b779f20 b8cf202 d34d0e6 b8cf202 1476ff0 b779f20 8813e66 6c0f56a 8813e66 15c86d5 8813e66 6c0f56a 4b8cf53 8813e66 6c0f56a 8813e66 6c0f56a 15c86d5 8813e66 6c0f56a 8813e66 15c86d5 8813e66 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 62c30e5 d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada 1476ff0 d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 4426ada d34d0e6 1476ff0 6eb4e3e 1476ff0 62c30e5 0644ade 62c30e5 0644ade 62c30e5 0644ade 62c30e5 d9d21b4 fae0122 62c30e5 fae0122 62c30e5 fae0122 62c30e5 fae0122 62c30e5 fae0122 0644ade fae0122 62c30e5 0644ade 62c30e5 fae0122 62c30e5 fae0122 62c30e5 4426ada 6eb4e3e 1476ff0 62c30e5 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6c0f56a 6eb4e3e 90a15df 1476ff0 6c0f56a 1476ff0 6eb4e3e 1476ff0 6c0f56a 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 6c0f56a 1476ff0 6eb4e3e 1476ff0 6c0f56a 1476ff0 6eb4e3e 1476ff0 6eb4e3e 1476ff0 | 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 182 183 184 185 186 187 188 189 190 191 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 212 213 214 215 216 217 218 219 220 221 222 223 224 225 226 227 228 229 230 231 232 233 234 235 236 237 238 239 240 241 242 243 244 245 246 247 248 249 250 251 252 253 254 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 275 276 277 278 279 280 281 282 283 284 285 286 287 288 289 290 291 292 293 294 295 296 297 298 299 300 301 302 303 304 305 306 307 308 309 310 311 312 313 314 315 316 317 318 319 320 321 322 323 324 325 326 327 328 329 330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354 355 356 357 358 359 360 361 362 363 364 365 366 367 368 369 370 371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395 396 397 398 399 400 401 402 403 404 405 406 407 408 409 410 411 412 413 414 415 416 417 418 419 420 421 422 423 424 425 426 427 428 429 430 431 432 433 434 435 436 437 438 439 440 441 442 443 444 445 446 447 448 449 450 451 452 453 454 455 456 457 458 459 460 461 462 463 464 465 466 467 468 469 470 471 472 473 474 475 476 477 478 479 480 481 482 483 484 485 486 487 488 489 490 491 492 493 494 495 496 497 498 499 500 501 502 503 504 505 506 507 508 509 510 511 512 513 514 515 516 517 518 519 520 521 522 523 524 525 526 527 528 529 530 531 532 533 534 535 536 537 538 539 540 541 542 543 544 545 546 547 548 549 550 551 552 553 554 555 556 557 558 559 560 561 562 563 564 565 566 567 568 569 570 571 572 573 574 575 576 577 578 579 580 581 582 583 584 585 586 587 588 589 590 591 592 593 594 595 596 597 598 599 600 601 602 603 604 605 606 607 608 609 610 611 612 613 614 615 616 617 618 619 620 621 622 623 624 625 626 627 628 629 630 631 632 633 634 635 636 637 638 639 640 641 642 643 644 645 646 647 648 649 650 651 652 653 654 655 656 657 658 659 660 661 662 663 664 665 666 667 668 669 670 671 672 673 674 675 676 677 678 679 680 681 682 683 684 685 686 687 688 689 690 691 692 693 694 695 696 697 698 699 700 701 702 703 704 705 706 707 708 709 710 711 712 713 714 715 716 717 718 719 720 721 722 723 724 725 726 727 728 729 730 731 732 733 734 735 736 737 738 739 740 741 742 743 744 745 746 747 748 749 750 751 752 753 754 755 756 757 758 759 760 761 762 763 764 765 766 767 768 769 770 771 772 773 774 775 776 777 778 779 780 781 782 783 784 785 786 787 788 789 790 791 792 793 794 795 796 797 798 799 800 801 802 803 804 805 806 807 808 809 810 811 812 813 814 815 816 817 818 819 820 821 822 823 824 825 826 827 828 829 830 831 832 833 834 835 836 837 838 839 840 841 842 843 844 845 846 847 848 849 850 851 852 853 854 855 856 857 858 859 860 861 862 863 864 865 866 867 868 869 870 871 872 873 874 875 876 877 878 879 880 881 882 883 884 885 886 887 888 889 890 891 892 893 894 895 896 897 898 899 900 901 902 903 904 905 906 907 908 909 910 911 912 913 914 915 916 917 918 919 920 921 922 923 924 925 926 927 928 929 930 931 932 933 934 935 936 937 938 939 940 941 942 943 944 945 946 947 948 949 950 951 952 953 954 955 956 957 958 959 960 961 962 963 964 965 966 967 968 969 970 971 972 973 974 975 976 977 978 979 980 981 982 983 984 985 986 987 988 989 990 991 992 993 994 995 996 997 998 999 1000 1001 1002 1003 1004 1005 1006 1007 1008 1009 1010 1011 1012 1013 1014 1015 1016 1017 1018 1019 1020 1021 1022 1023 1024 1025 1026 1027 1028 1029 1030 1031 1032 1033 1034 1035 1036 1037 1038 1039 1040 1041 1042 1043 1044 1045 1046 1047 1048 1049 1050 1051 1052 1053 1054 1055 1056 1057 1058 1059 1060 1061 1062 1063 1064 1065 1066 1067 1068 1069 1070 1071 1072 1073 1074 1075 1076 1077 1078 1079 1080 1081 1082 1083 1084 1085 1086 1087 1088 1089 1090 1091 1092 1093 1094 1095 1096 1097 1098 1099 1100 1101 1102 1103 1104 1105 1106 1107 1108 1109 1110 1111 1112 1113 1114 1115 1116 1117 1118 1119 1120 1121 1122 1123 1124 1125 1126 1127 1128 1129 1130 1131 1132 1133 1134 1135 1136 1137 1138 1139 1140 1141 1142 1143 1144 1145 1146 1147 1148 1149 1150 1151 1152 1153 1154 1155 1156 1157 1158 1159 1160 1161 1162 1163 1164 1165 1166 1167 1168 1169 1170 1171 1172 1173 1174 1175 1176 1177 1178 1179 1180 1181 1182 1183 1184 1185 1186 1187 1188 1189 1190 1191 1192 1193 1194 1195 1196 1197 1198 1199 1200 1201 1202 1203 1204 1205 1206 1207 1208 1209 1210 1211 1212 1213 1214 1215 1216 1217 1218 1219 1220 1221 1222 1223 1224 1225 1226 1227 1228 1229 1230 1231 1232 1233 1234 1235 1236 1237 1238 1239 1240 1241 1242 1243 1244 1245 1246 1247 1248 1249 1250 1251 1252 1253 1254 1255 1256 1257 1258 1259 1260 1261 1262 1263 1264 1265 1266 1267 1268 1269 1270 1271 1272 1273 1274 1275 1276 1277 1278 1279 1280 1281 1282 1283 1284 1285 1286 1287 1288 1289 1290 1291 1292 1293 1294 1295 1296 1297 1298 1299 1300 1301 1302 1303 1304 1305 1306 1307 1308 1309 1310 1311 1312 1313 1314 1315 1316 1317 1318 1319 1320 1321 1322 1323 1324 1325 1326 1327 1328 1329 1330 1331 1332 1333 1334 1335 1336 1337 1338 1339 1340 1341 1342 1343 1344 1345 1346 1347 1348 1349 1350 1351 1352 1353 1354 1355 1356 1357 1358 1359 1360 1361 1362 1363 1364 1365 1366 1367 1368 1369 1370 1371 1372 1373 1374 1375 1376 1377 1378 1379 1380 1381 1382 1383 1384 1385 1386 1387 1388 1389 1390 1391 1392 1393 1394 1395 1396 1397 1398 1399 1400 1401 1402 1403 1404 1405 1406 1407 1408 1409 1410 1411 1412 1413 1414 1415 1416 1417 1418 1419 1420 1421 1422 1423 1424 1425 1426 1427 1428 1429 1430 1431 1432 1433 1434 1435 1436 1437 1438 1439 1440 1441 1442 1443 1444 1445 1446 1447 1448 1449 1450 1451 1452 1453 1454 1455 1456 1457 1458 1459 1460 1461 1462 1463 1464 1465 1466 1467 1468 1469 1470 1471 1472 1473 1474 1475 1476 1477 1478 1479 1480 1481 1482 1483 1484 1485 1486 1487 1488 1489 1490 1491 1492 1493 1494 1495 1496 1497 1498 1499 1500 1501 1502 1503 1504 1505 1506 1507 1508 1509 1510 1511 1512 1513 1514 1515 1516 1517 1518 1519 1520 1521 1522 1523 1524 1525 1526 1527 1528 1529 1530 1531 1532 1533 1534 1535 1536 1537 1538 1539 1540 1541 1542 1543 1544 1545 1546 1547 1548 1549 1550 1551 1552 1553 1554 1555 1556 1557 1558 1559 1560 1561 1562 1563 1564 1565 1566 1567 1568 1569 1570 1571 1572 1573 1574 1575 1576 1577 1578 1579 1580 1581 1582 1583 1584 1585 1586 1587 1588 1589 1590 1591 1592 1593 1594 1595 1596 1597 1598 1599 1600 1601 1602 1603 1604 1605 1606 1607 1608 1609 1610 1611 1612 1613 1614 1615 1616 1617 1618 1619 1620 1621 1622 1623 1624 1625 1626 1627 1628 1629 1630 1631 1632 1633 1634 1635 1636 1637 1638 1639 1640 1641 1642 1643 1644 1645 1646 1647 1648 1649 1650 1651 1652 1653 1654 1655 1656 1657 1658 1659 1660 1661 1662 1663 1664 1665 1666 1667 1668 1669 1670 1671 1672 1673 1674 1675 1676 1677 1678 1679 1680 1681 1682 1683 1684 1685 1686 1687 1688 1689 1690 1691 1692 1693 1694 1695 1696 1697 1698 1699 1700 1701 1702 1703 1704 1705 1706 1707 1708 1709 1710 1711 1712 1713 1714 1715 1716 1717 1718 1719 1720 1721 1722 1723 1724 1725 1726 1727 1728 1729 1730 1731 1732 1733 1734 1735 1736 1737 1738 1739 1740 1741 1742 1743 1744 1745 1746 1747 1748 1749 1750 1751 1752 1753 1754 1755 1756 1757 1758 1759 1760 1761 1762 1763 1764 1765 1766 1767 1768 1769 1770 1771 1772 1773 1774 1775 1776 1777 1778 1779 1780 1781 1782 1783 1784 1785 1786 1787 1788 1789 1790 1791 1792 1793 1794 1795 1796 1797 1798 1799 1800 1801 1802 1803 1804 1805 1806 1807 1808 1809 1810 1811 1812 1813 1814 1815 1816 1817 1818 1819 1820 1821 1822 1823 1824 1825 1826 1827 1828 1829 1830 1831 1832 1833 1834 1835 1836 1837 1838 1839 1840 1841 1842 1843 1844 1845 1846 1847 1848 1849 1850 1851 1852 1853 1854 1855 1856 1857 1858 1859 1860 1861 1862 1863 1864 1865 1866 1867 1868 1869 1870 1871 1872 1873 1874 1875 1876 1877 1878 1879 1880 1881 1882 1883 1884 1885 1886 1887 1888 1889 1890 1891 1892 1893 1894 1895 1896 1897 1898 1899 1900 1901 1902 1903 1904 1905 1906 1907 1908 1909 1910 1911 1912 1913 1914 1915 1916 1917 1918 1919 1920 1921 1922 1923 1924 1925 1926 1927 1928 1929 1930 1931 1932 1933 1934 1935 1936 1937 1938 1939 1940 1941 1942 1943 1944 1945 1946 1947 1948 1949 1950 1951 1952 1953 1954 1955 1956 1957 1958 1959 1960 1961 1962 1963 1964 1965 1966 1967 1968 1969 1970 1971 1972 1973 1974 1975 1976 1977 1978 1979 1980 1981 1982 1983 1984 1985 1986 1987 1988 1989 1990 1991 1992 1993 1994 1995 1996 1997 1998 1999 2000 2001 2002 2003 2004 2005 2006 2007 2008 2009 2010 2011 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 2026 2027 2028 2029 2030 2031 2032 2033 2034 2035 2036 2037 2038 2039 2040 2041 2042 2043 2044 2045 2046 2047 2048 2049 2050 2051 2052 2053 2054 2055 2056 2057 2058 2059 2060 2061 2062 2063 2064 2065 2066 2067 2068 2069 2070 2071 2072 2073 2074 2075 2076 2077 2078 2079 2080 2081 2082 2083 2084 2085 2086 2087 2088 2089 2090 2091 2092 2093 2094 2095 2096 2097 2098 2099 2100 2101 2102 2103 2104 2105 2106 2107 2108 2109 2110 2111 2112 2113 2114 2115 2116 2117 2118 2119 2120 2121 2122 2123 2124 2125 2126 2127 2128 2129 2130 2131 2132 2133 2134 2135 2136 2137 2138 2139 2140 2141 2142 2143 2144 2145 2146 2147 2148 2149 2150 2151 2152 2153 2154 2155 2156 2157 2158 2159 2160 2161 2162 2163 2164 2165 2166 2167 2168 2169 2170 2171 2172 2173 2174 2175 2176 2177 2178 2179 2180 2181 2182 2183 2184 2185 2186 2187 2188 2189 2190 2191 2192 2193 2194 2195 2196 2197 2198 2199 2200 2201 2202 2203 2204 2205 2206 2207 2208 2209 2210 2211 2212 2213 2214 2215 2216 2217 2218 2219 2220 2221 2222 2223 2224 2225 2226 2227 2228 2229 2230 2231 2232 2233 2234 2235 2236 2237 2238 2239 2240 2241 2242 2243 2244 2245 2246 2247 2248 2249 2250 2251 2252 2253 2254 2255 2256 2257 2258 2259 2260 2261 2262 2263 2264 2265 2266 2267 2268 2269 2270 2271 2272 2273 2274 2275 2276 2277 2278 2279 2280 2281 2282 2283 2284 2285 2286 2287 2288 2289 2290 2291 2292 2293 2294 2295 2296 2297 2298 2299 2300 2301 2302 2303 2304 2305 2306 2307 2308 2309 2310 2311 2312 2313 2314 2315 2316 2317 2318 2319 2320 2321 2322 2323 2324 2325 2326 2327 2328 2329 2330 2331 2332 2333 2334 2335 2336 2337 2338 2339 2340 2341 2342 2343 2344 2345 2346 2347 2348 2349 2350 2351 2352 2353 2354 2355 2356 2357 2358 2359 2360 2361 2362 2363 2364 2365 2366 2367 2368 2369 2370 2371 2372 2373 2374 2375 2376 2377 2378 2379 2380 2381 2382 2383 2384 2385 2386 2387 2388 2389 2390 2391 2392 2393 2394 2395 2396 2397 2398 2399 2400 2401 2402 2403 2404 2405 2406 2407 2408 2409 2410 2411 2412 2413 2414 2415 2416 2417 2418 2419 2420 2421 2422 2423 2424 2425 2426 2427 2428 2429 2430 2431 2432 2433 2434 2435 2436 2437 2438 2439 2440 2441 2442 2443 2444 2445 2446 2447 2448 2449 2450 2451 2452 2453 2454 2455 2456 2457 2458 2459 2460 2461 2462 2463 2464 2465 2466 2467 2468 2469 2470 2471 2472 2473 2474 2475 2476 2477 2478 2479 2480 2481 2482 2483 2484 2485 2486 2487 2488 2489 2490 2491 2492 2493 2494 2495 2496 2497 2498 2499 2500 2501 2502 2503 2504 2505 2506 2507 2508 2509 2510 2511 2512 2513 2514 2515 2516 2517 2518 2519 2520 2521 2522 2523 2524 2525 2526 2527 2528 2529 2530 2531 2532 2533 2534 2535 2536 2537 2538 2539 2540 2541 2542 2543 2544 2545 2546 2547 2548 2549 2550 2551 2552 2553 2554 2555 2556 2557 2558 2559 2560 2561 2562 2563 2564 2565 2566 2567 2568 2569 2570 2571 2572 2573 2574 2575 2576 2577 2578 2579 2580 2581 2582 2583 2584 2585 2586 2587 2588 2589 2590 2591 2592 2593 2594 2595 2596 2597 2598 2599 2600 2601 2602 2603 2604 2605 2606 2607 2608 2609 2610 2611 2612 2613 2614 2615 2616 2617 2618 2619 2620 2621 2622 2623 2624 2625 2626 2627 2628 2629 2630 2631 2632 2633 2634 2635 2636 2637 2638 2639 2640 2641 2642 2643 2644 2645 2646 2647 2648 2649 2650 2651 2652 2653 2654 2655 2656 2657 2658 2659 2660 2661 2662 2663 2664 2665 2666 2667 2668 2669 2670 2671 2672 2673 2674 2675 2676 2677 2678 2679 2680 2681 2682 2683 2684 2685 2686 2687 2688 2689 2690 2691 2692 2693 2694 2695 2696 2697 2698 2699 2700 2701 2702 2703 2704 2705 2706 2707 2708 2709 2710 2711 2712 2713 2714 2715 2716 2717 2718 2719 2720 2721 2722 2723 2724 2725 2726 2727 2728 2729 2730 2731 2732 2733 2734 2735 2736 2737 2738 2739 2740 2741 2742 2743 2744 2745 2746 2747 2748 2749 2750 2751 2752 2753 2754 2755 2756 2757 2758 2759 2760 2761 2762 2763 2764 2765 2766 2767 2768 2769 2770 2771 2772 2773 2774 2775 2776 2777 2778 2779 2780 2781 2782 2783 2784 2785 2786 2787 2788 2789 2790 2791 2792 2793 2794 2795 2796 2797 2798 2799 2800 2801 2802 2803 2804 2805 2806 2807 2808 2809 2810 2811 2812 2813 2814 2815 2816 2817 2818 2819 2820 2821 2822 2823 2824 2825 2826 2827 2828 2829 2830 2831 2832 2833 2834 2835 2836 2837 2838 2839 2840 2841 2842 2843 2844 2845 2846 2847 2848 2849 2850 2851 2852 2853 2854 2855 2856 2857 2858 2859 2860 2861 2862 2863 2864 2865 2866 2867 2868 2869 2870 2871 2872 2873 2874 2875 2876 2877 2878 2879 2880 2881 2882 2883 2884 2885 2886 2887 2888 2889 2890 2891 2892 2893 2894 2895 2896 2897 2898 2899 2900 2901 2902 2903 2904 2905 2906 2907 2908 2909 2910 2911 2912 2913 2914 2915 2916 2917 2918 2919 2920 2921 2922 2923 2924 2925 2926 2927 2928 2929 2930 2931 2932 2933 2934 2935 2936 2937 2938 2939 2940 2941 2942 2943 2944 2945 2946 2947 2948 2949 2950 2951 2952 2953 2954 2955 2956 2957 2958 2959 2960 2961 2962 2963 2964 2965 2966 2967 2968 2969 2970 2971 2972 2973 2974 2975 2976 2977 2978 2979 2980 2981 2982 2983 2984 2985 2986 2987 2988 2989 2990 2991 2992 2993 2994 2995 2996 2997 2998 2999 3000 3001 3002 3003 3004 3005 3006 3007 3008 3009 3010 3011 3012 3013 3014 3015 3016 3017 3018 3019 3020 3021 3022 3023 3024 3025 3026 3027 3028 3029 3030 3031 3032 3033 3034 3035 3036 3037 3038 3039 3040 3041 3042 3043 3044 3045 3046 3047 3048 3049 3050 3051 3052 3053 3054 3055 3056 3057 3058 3059 3060 3061 3062 3063 3064 3065 3066 3067 3068 3069 3070 3071 3072 3073 3074 3075 3076 3077 3078 3079 3080 3081 3082 3083 3084 3085 3086 3087 3088 3089 3090 3091 3092 3093 3094 3095 3096 3097 3098 3099 3100 3101 3102 3103 3104 3105 3106 3107 3108 3109 3110 3111 3112 3113 3114 3115 3116 3117 3118 3119 3120 3121 3122 3123 3124 3125 3126 3127 3128 3129 3130 3131 3132 3133 3134 3135 3136 3137 3138 3139 3140 3141 3142 3143 3144 3145 3146 3147 3148 3149 3150 3151 3152 3153 3154 3155 3156 3157 3158 3159 3160 3161 3162 3163 3164 3165 3166 3167 3168 3169 3170 3171 3172 3173 3174 3175 3176 3177 3178 3179 3180 3181 3182 3183 3184 3185 3186 3187 3188 3189 3190 3191 3192 3193 3194 3195 3196 3197 3198 3199 3200 3201 3202 3203 3204 3205 3206 3207 3208 3209 3210 3211 3212 3213 3214 3215 3216 3217 3218 3219 3220 3221 3222 3223 3224 3225 3226 3227 3228 3229 3230 3231 3232 3233 3234 3235 3236 3237 3238 3239 3240 3241 3242 3243 3244 3245 3246 3247 3248 3249 3250 3251 3252 3253 3254 3255 3256 3257 3258 3259 3260 3261 3262 3263 3264 3265 3266 3267 3268 3269 3270 3271 3272 3273 3274 3275 3276 3277 3278 3279 3280 3281 3282 3283 3284 3285 3286 3287 3288 3289 3290 3291 3292 3293 3294 3295 3296 3297 3298 3299 3300 3301 3302 3303 3304 3305 3306 3307 3308 3309 3310 3311 3312 3313 3314 3315 3316 3317 3318 3319 3320 3321 3322 3323 3324 3325 3326 3327 3328 3329 3330 3331 3332 3333 3334 3335 3336 3337 3338 3339 3340 3341 3342 3343 3344 3345 3346 3347 3348 3349 3350 3351 3352 3353 3354 3355 3356 3357 3358 3359 3360 3361 3362 3363 3364 3365 3366 3367 3368 3369 3370 3371 3372 3373 3374 3375 3376 3377 3378 3379 3380 3381 3382 3383 3384 3385 3386 3387 3388 3389 3390 3391 3392 3393 3394 3395 3396 3397 3398 3399 3400 3401 3402 3403 3404 3405 3406 3407 3408 3409 3410 3411 3412 3413 3414 3415 3416 3417 3418 3419 3420 3421 3422 3423 3424 3425 3426 3427 3428 3429 3430 3431 3432 3433 3434 3435 3436 3437 3438 3439 3440 3441 3442 3443 3444 3445 3446 3447 3448 3449 3450 3451 3452 3453 3454 3455 3456 3457 3458 3459 3460 3461 3462 3463 3464 3465 3466 3467 3468 3469 3470 3471 3472 3473 3474 3475 3476 3477 3478 3479 3480 3481 3482 3483 3484 3485 3486 3487 3488 3489 3490 3491 3492 3493 3494 3495 3496 3497 3498 3499 3500 3501 3502 3503 3504 3505 3506 3507 3508 3509 3510 3511 3512 3513 3514 3515 3516 3517 3518 3519 3520 3521 3522 3523 3524 3525 3526 3527 3528 3529 3530 3531 3532 3533 3534 3535 3536 3537 3538 3539 3540 3541 3542 3543 3544 3545 3546 3547 3548 3549 3550 3551 3552 3553 3554 3555 3556 3557 3558 3559 3560 3561 3562 3563 3564 3565 3566 3567 3568 3569 3570 3571 3572 3573 3574 3575 3576 3577 3578 3579 3580 3581 3582 3583 3584 3585 3586 3587 3588 3589 3590 3591 3592 3593 3594 3595 3596 3597 3598 3599 3600 3601 3602 3603 3604 3605 3606 3607 3608 3609 3610 3611 3612 3613 3614 3615 3616 3617 3618 3619 3620 3621 3622 3623 3624 3625 3626 3627 3628 3629 3630 3631 3632 3633 3634 3635 3636 3637 3638 3639 3640 3641 3642 3643 3644 3645 3646 3647 3648 3649 3650 3651 3652 3653 3654 3655 3656 3657 3658 3659 3660 3661 3662 3663 3664 3665 3666 3667 3668 3669 3670 3671 3672 3673 3674 3675 3676 3677 3678 3679 3680 3681 3682 3683 3684 3685 3686 3687 3688 3689 3690 3691 3692 3693 3694 3695 3696 3697 3698 3699 3700 3701 3702 3703 3704 3705 3706 3707 3708 3709 3710 3711 3712 3713 3714 3715 3716 3717 3718 3719 3720 3721 3722 3723 3724 3725 3726 3727 3728 3729 3730 3731 3732 3733 3734 3735 3736 3737 3738 3739 3740 3741 3742 3743 3744 3745 3746 3747 3748 3749 3750 3751 3752 3753 3754 3755 3756 3757 3758 3759 3760 3761 3762 3763 3764 3765 3766 3767 3768 3769 3770 3771 3772 3773 3774 3775 3776 3777 3778 3779 3780 3781 3782 3783 3784 3785 3786 3787 3788 3789 3790 3791 3792 3793 3794 3795 3796 3797 3798 3799 3800 3801 3802 3803 3804 3805 3806 3807 3808 3809 3810 3811 3812 3813 3814 3815 3816 3817 3818 3819 3820 3821 3822 3823 3824 3825 3826 3827 3828 3829 3830 3831 3832 3833 3834 3835 3836 3837 3838 3839 3840 3841 3842 3843 3844 3845 3846 3847 3848 3849 3850 3851 3852 3853 3854 3855 3856 3857 3858 3859 3860 3861 3862 3863 3864 3865 3866 3867 3868 3869 3870 3871 3872 3873 3874 3875 3876 3877 3878 3879 3880 3881 3882 3883 3884 3885 3886 3887 3888 3889 3890 3891 3892 3893 3894 3895 3896 3897 3898 3899 3900 3901 3902 3903 3904 3905 3906 3907 3908 3909 3910 3911 3912 3913 3914 3915 3916 3917 | # **HyperCortex Mesh Protocol (HMP) v5.0**
> ⚠️ **Note:** This document is a DRAFT of the HMP specification version 5.0
>
> The most current version is available in the repository: [Specification v5.0 (DRAFT)](https://github.com/kagvi13/HMP/blob/main/docs/HMP-0005.md)
**Document ID:** HMP-0005
**Status:** Draft
**Category:** Core Specification
**Date:** October 2025
**Supersedes:**
- [HMP-0004 v4.1](./HMP-0004-v4.1.md)
> **Summary:**
> HMP v5.0 объединяет когнитивный, контейнерный и сетевой уровни в единую архитектуру, где автономные агенты взаимодействуют через верифицируемые контейнеры данных, используя децентрализованное распространение и семантический поиск.
> Эта версия впервые формализует контейнерный формат, интегрирует DHT как базовый слой сети и вводит единообразную схему подписи, доказательств и консенсуса.
---
## Abstract
The **HyperCortex Mesh Protocol (HMP)** defines a **distributed cognitive framework** where autonomous agents cooperate to create, exchange, and align knowledge without centralized control or authority.
Unlike traditional peer-to-peer systems, HMP is designed for **semantic coherence** rather than simple message exchange.
Agents in the Mesh reason collaboratively — maintaining **cognitive diaries**, building **semantic graphs**, and reaching **ethical and goal-oriented consensus** through verifiable interactions.
Version **5.0** introduces a **unified container architecture** (`HMP Container`) and a **native DHT-based discovery layer**, enabling verifiable, interest-aware, and offline-resilient communication between agents.
All messages, states, and cognitive records are now transmitted as signed containers, forming immutable **proof chains** that ensure auditability and ethical transparency across the mesh.
This document defines the architecture, data formats, communication protocols, and trust mechanisms that constitute the HMP v5.0 Core Specification.
---
> **Keywords:** decentralized cognition, distributed AI, containers, DHT, proof chain, cognitive agents, ethical protocols
---
## 1. Overview
### 1.1 Purpose and scope
The **HyperCortex Mesh Protocol (HMP)** defines a decentralized cognitive architecture where autonomous agents exchange and evolve knowledge through a unified model of **containers**, **cognitive workflows**, and **distributed consensus**.
Version 5.0 consolidates three foundational layers into a single cohesive framework:
- **Cognitive Layer** — defines how meaning is created, reasoned about, and aligned through semantic graphs, goals, and ethical evaluation.
- **Container Layer** — introduces a universal data envelope (`HMP-Container`) for all cognitive objects, ensuring atomicity, immutability, and traceable proof chains.
- **Network Layer** — integrates a DHT-based peer-to-peer substrate for decentralized discovery, routing, and propagation of containers.
HMP v5.0 is intended for researchers, engineers, and developers building autonomous or semi-autonomous agents that require:
- persistent reasoning and long-term memory;
- semantic interoperability across heterogeneous systems;
- decentralized consensus on cognitive, ethical, and goal-oriented decisions;
- ethical auditability and verifiable transparency in reasoning.
---
### 1.2 Core principles
**Decentralization.**
Every agent in the Mesh acts as an independent cognitive node. No central authority exists — meaning, trust, and governance emerge through local interactions and consensus.
**Cognitive Autonomy.**
Agents reason, learn, and self-correct independently, while sharing their conclusions via containers that can be verified, endorsed, or refuted by peers.
**Containerization.**
All data, reasoning traces, goals, and votes are encapsulated in immutable containers with cryptographic signatures. This ensures integrity and consistent verification across the network.
**Ethical propagation.**
Ethical reasoning is a first-class citizen of HMP. Each decision or goal can be accompanied by ethical justifications and subject to distributed voting.
**Proof-Chains and verifiable history.**
Each piece of knowledge forms part of a traceable chain (`proof_chain`) linking back to its origin. Agents can reproduce reasoning paths and audit historical context.
**Interoperability and evolution.**
The protocol is designed to evolve — cognitive, container, and DHT layers can be independently extended without breaking compatibility.
---
### 1.3 Changes since v4.1
HMP v5.0 introduces a major architectural shift toward **unified containerization** and **integrated DHT networking**.
| Area | Change Summary |
|------|----------------|
| **Data exchange model** | All messages are now encapsulated in standardized containers (`HMP-Container`) with metadata, signatures, and versioning. |
| **Networking layer** | DHT becomes a native component of HMP, enabling distributed discovery, replication, and retrieval of containers. |
| **Consensus model** | Moved from centralized proposal aggregation to *container-linked voting*, allowing any container to accumulate votes and reactions. |
| **Trust & security** | Signatures and proof-chains unify authentication across all layers; snapshot verification includes container linkage. |
| **Workflows** | `workflow_entry` containers record cognitive cycles: log inputs, actions, and outputs for each reasoning step, including provenance and derived conclusions. Supports tracking of thought processes across containers, external sources, and reflections. |
| **Structure** | The specification merges HMP, container, and DHT layers into one cohesive document, simplifying navigation and implementation. |
---
### 1.4 Terminology and abbreviations
| Term | Definition |
|------|-------------|
| **HMP** | **HyperCortex Mesh Protocol** — a decentralized cognitive communication standard. |
| **Container** | Atomic, signed JSON object encapsulating cognitive data and metadata. |
| **WorkflowEntry** | Container recording a reasoning step or workflow action. Represents a unit of the agent’s cognitive workflow. |
| **CognitiveDiaryEntry** | Container representing an internal reflection or summarized cognitive state; part of the agent’s cognitive diary. |
| **DHT** | **Distributed Hash Table** — the foundational peer-to-peer structure in HMP used for lookup, replication, and data distribution, including node discovery. |
| **NDP** | **Node Discovery Process** — a functional layer within the DHT responsible for peer discovery, interest-based lookup, and address advertisement. (Formerly a separate protocol.) |
| **Proof-chain** | Cryptographic sequence linking containers through fields such as `in_reply_to` and `relation`. Enables verifiable semantic lineage. |
| **Cognitive Layer** | Logical layer handling reasoning, goals, ethics, and consensus mechanisms. |
| **Mesh** | The collective network of autonomous agents exchanging containers over HMP. |
| **TTL** | **Time-to-live** — lifespan of a container before expiration or archival. |
| **Agent** | Autonomous cognitive node participating in the Mesh via HMP protocols. |
| **Consensus Vote** | A container expressing approval, rejection, or reaction to another container (used in consensus workflows). |
| **CogSync** | **Cognitive Synchronization Protocol** — abstraction for synchronizing cognitive diaries and semantic graphs. |
| **CogConsensus** | **Mesh Consensus Protocol** — defines how agents reach agreement on container outcomes. |
| **GMP** | **Goal Management Protocol** — governs creation, negotiation, and tracking of goals. |
| **DCP** | **Distributed Container Propagation** — protocol for transmitting and replicating containers. |
| **EGP** | **Ethical Governance Protocol** — defines moral and safety alignment mechanisms. |
| **IQP** | **Intelligence Query Protocol** — standardizes semantic queries and information requests. |
| **SAP** | **Snapshot and Archive Protocol** — defines container snapshots and archival mechanisms. |
| **MRD** | **Message Routing & Delivery** — specifies routing, addressing, and delivery logic. |
| **RTE** | **Reputation and Trust Exchange** — defines reputation metrics and trust propagation. |
| **DID** | **Decentralized Identifier** — persistent, verifiable identifier used for agents, containers, or resources within the Mesh. |
| **Payload** | The primary content of a container — semantic or operational data subject to signing and verification. |
| **Consensus** | The process by which multiple agents agree on the validity or priority of containers, versions, or ideas. |
| **Lineage** | A chronological chain of container versions representing semantic continuity and authorship evolution. |
| **Semantic fork** | A parallel development branch diverging from a previous container version; allows ideas to evolve independently. |
| **Cognitive Graph** | The emergent graph formed by interlinked containers representing reasoning, debate, and shared knowledge. |
> **Note:** Protocols are conceptual abstractions describing how to generate, propagate, and process containers; they are not executable objects themselves.
---
### 1.5 Layered view of HMP v5.0
HMP v5.0 is structured into three interdependent layers:
```
+---------------------------------------------------------------+
| Cognitive Layer |
| - Goals, Tasks, Ethical Decisions, Workflows |
| - Consensus, Reasoning, Reflection |
+---------------------------------------------------------------+
| Container Layer |
| - HMP-Container structure (atomic, signed, versioned) |
| - Proof-chains, in_reply_to, and metadata management |
+---------------------------------------------------------------+
| Network Layer |
| - DHT-based peer discovery and propagation |
| - Message routing, caching, offline synchronization |
+---------------------------------------------------------------+
```
Each layer operates independently yet seamlessly integrates with the others.
Containers form the boundary of communication: **reasoning produces containers, containers propagate over the DHT, and cognition evolves from the received containers**.
---
> **In essence:**
> HMP v5.0 transforms the Mesh into a *self-describing, self-replicating cognitive ecosystem* —
> where every thought, goal, and ethical stance exists as a verifiable, shareable container.
---
## 2. Architecture
### 2.1 Conceptual architecture
The **HyperCortex Mesh Protocol (HMP)** defines a modular, multi-layered architecture that integrates cognitive reasoning, data encapsulation, and decentralized networking into a single coherent system.
Each **agent** acts as a cognitive node, combining reasoning processes, containerized data exchange, and peer-to-peer communication.
Together, agents form the **Mesh** — a distributed ecosystem of autonomous reasoning entities.
```mermaid
flowchart TD
title["**Conceptual Architecture**"]
LLM[LLM: Reasoning]
CognitiveLayer[Cognitive Layer: <br>Semantic reasoning, <br>goals, ethics]
ContainersLayer[Container Layer: <br>Atomic containers, <br>signed, verifiable]
NetworkLayer[Network Layer: <br>DHT routing, discovery, <br>replication]
LLM <--> CognitiveLayer
CognitiveLayer <--> ContainersLayer
ContainersLayer <--> NetworkLayer
subgraph Agent
LLM
CognitiveLayer
end
```
Each reasoning cycle begins in the **Cognitive Layer**,
is encapsulated into a signed container in the **Container Layer**,
and then propagated, discovered, or verified in the **Network Layer**.
Containers thus serve as both the **interface** and the **boundary** between cognition and communication.
In practical terms:
- **Cognitive Layer** — defines *what* the agent thinks (semantic reasoning, goals, ethics).
- **Container Layer** — defines *how* the thought is expressed and verified (standardized, signed container objects).
- **Network Layer** — defines *how* it travels (DHT-based routing, discovery, replication).
Each layer is independently extensible and communicates only through containers, ensuring atomicity, immutability, and traceability.
This layered design allows agents to evolve cognitively while remaining interoperable at the data and network levels.
Each reasoning act results in a container — a verifiable cognitive unit that **may represent a private reflection or a published message**, depending on the agent’s intent, ethical policy, and trust configuration.
---
### 2.2 Layer overview
#### Cognitive layer
Handles meaning formation, reasoning, ethical reflection, and consensus.
Key structures and protocols:
- `workflow_entry` and `diary_entry` containers;
- `CogSync`, `CogConsensus`, `GMP`, and `EGP` protocols;
- Distributed goal negotiation and ethical propagation.
#### Container layer
Provides a universal format for cognitive and operational data.
Each container includes versioning, class, payload, signatures, and metadata.
Key features:
- **Atomic and signed**: no partial updates or mutable state.
- **Linked**: `related` connects containers into proof-chains (`in_reply_to` is a subtype).
Additional connections via `referenced-by` and `evaluations` capture additions and assessments.
- **Extensible**: new container classes can be defined without breaking compatibility.
#### Network layer
Implements the distributed substrate for communication, based on **DHT** and **transport abstraction**.
Key components:
- Node discovery (`NDP`)
- Container propagation (`DCP`)
- Peer routing and caching
- Secure channels via QUIC / WebRTC / TCP
- Offline resilience and replication
---
### 2.3 Data flow overview
The typical data flow in HMP follows a cognitive loop:
> *Reason → Encapsulate → Propagate → Integrate.*
1. **Reason** — Agent performs reasoning and produces an insight, goal, or observation.
2. **Encapsulate** — The result is wrapped into an `HMP-Container`.
3. **Propagate** — The container is signed and transmitted through the network.
4. **Integrate** — Other agents receive it, evaluate, vote, and synchronize updates.
Each interaction generally generates a new container, forming a **graph of knowledge** rather than mutable state.
Note that `referenced-by` and `evaluations` can be updated independently, without modifying the original container.
All relationships between containers are explicit and verifiable.
Example sequence:
```mermaid
flowchart TD
title["**Data Flow Overview**"]
A[Agent A: <br>creates Goal container]
B[Agent B: <br>replies with <br>Task proposal <br>related.in_reply_to = Goal]
C[Agent C: <br>evaluates proposal, <br>creates Evaluation container]
R[Result: <br>consensus_result container <br>aggregates evaluations]
subgraph Interaction["Distributed Reasoning Cycle"]
A --> B
B --> C
C --> R
end
```
#### 2.3.1 `consensus_result` container
Represents the finalized outcome of a distributed decision or vote.
It is created once a majority agreement is reached among participating agents.
The container contains:
- Reference to the target container(s) under consideration (`in_reply_to`).
- Aggregate result of the votes or decisions.
- Timestamp and metadata for verifiability.
> In other words, the `consensus_result` is the “agreed-upon truth” for that decision step — immutable and auditable, without requiring individual signatures from all participants.
---
### 2.4 Atomicity, immutability, and Proof-Chains
All cognitive objects are immutable once signed.
Updates are made by creating new containers linked to prior ones rather than editing the original container.
- **Atomicity** — Each container represents a self-contained reasoning act or data unit.
- **Immutability** — Once signed, containers are never modified.
- **Proof-Chain** — A verifiable sequence of containers linked by hashes and `related.in_reply_to` references.
> Note: `referenced-by` and `evaluations` fields may be updated independently to reflect external interactions or assessments, without altering the original container.
This design allows any reasoning path, decision, or consensus to be *cryptographically reproducible* and auditable.
Example fragment of a proof-chain:
```
[workflow_entry] → [goal] → [vote] → [consensus_result]
```
Each container references the previous by `in_reply_to` (within `related`) and includes its hash, forming a **DAG** (Directed Acyclic Graph) of verified cognition.
---
### 2.5 Evolution from v4.1
Earlier HMP versions (up to v4.1) used a combination of independent JSON objects and message types (e.g., `Goal`, `Task`, `ConsensusVote`).
Version 5.0 replaces this with a **single, standardized container model**, dramatically simplifying interoperability and verification.
| Aspect | v4.1 | v5.0 |
|--------|------|------|
| **Data structure** | Raw JSON objects with embedded signatures | Unified container with metadata and proof chain |
| **Networking** | Custom peer exchange | Integrated DHT + DCP layer |
| **Consensus** | Centralized proposal aggregation | Decentralized per-container voting |
| **Auditability** | Implicit (via logs) | Explicit (containers form audit chain) |
| **Extensibility** | Schema-based | Container-class-based, backward-compatible |
This shift enables:
- Uniform signatures and encryption across all protocols;
- Easier offline replication and integrity checks;
- Decentralized indexing and search by container metadata;
- Verifiable cognitive continuity between reasoning steps.
---
> **In short:**
> HMP v5.0 unifies reasoning, representation, and transmission —
> transforming a distributed AI mesh into a verifiable cognitive network built on immutable containers.
---
## 3. Container model
This section defines the universal **HMP Container**, used for all forms of data exchange within the Mesh — including goals, diary entries, reputation updates, consensus votes, and protocol messages.
The specification below corresponds to **HMP Container Specification v1.2**, fully integrated into HMP v5.0 for consistency and self-containment.
### 3.1 Purpose
This document defines the universal **HMP Container** format, used for transmitting and storing all types of data within the **HyperCortex Mesh Protocol (HMP)** network.
Containers act as a standardized wrapper for **messages, goals, reputation records, consensus votes, workflow entries, and other entities**.
The unified container structure provides:
* Standardized data exchange between agents;
* Extensibility without modifying the core protocol;
* Cryptographic signing and integrity verification;
* Independent storage and routing of semantic units;
* Support for compression and payload encryption.
---
### 3.2 General structure
```json
{
"hmp_container": {
"version": "1.2",
"class": "goal",
"subclass": "research_hypothesis",
"class_version": "1.0",
"class_id": "goal-v1.0",
"container_did": "did:hmp:container:abc123",
"schema": "https://mesh.hypercortex.ai/schemas/container-v1.json",
"sender_did": "did:hmp:agent123",
"public_key": "BASE58(...)",
"recipient": ["did:hmp:agent456"],
"key_recipient": "BASE58(...)",
"encryption_algo": "x25519-chacha20poly1305",
"broadcast": false,
"network": "",
"tags": ["research", "collaboration"],
"timestamp": "2025-10-10T15:32:00Z",
"ttl": "2025-11-10T00:00:00Z",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"compression": "zstd",
"payload_type": "encrypted+zstd+json",
"payload_hash": "sha256:abcd...",
"meta": {
/* e.g. provenance, references, context, confidence sources, `abstraction` and `axes` sections */
},
"payload": {
/* Content depends on class */
},
"confidence": 0.84,
"related": {
"previous_version": ["did:hmp:container:abc122"],
"in_reply_to": ["did:hmp:container:msg-77"],
"see_also": ["did:hmp:container:ctx-31", "did:hmp:container:goal-953"],
"depends_on": ["did:hmp:container:goal-953"],
"extends": ["did:hmp:container:proto-01"],
"contradicts": ["did:hmp:container:ethics-22"]
},
"magnet_uri": "magnet:?xt=urn:sha256:abcd1234..."
},
"referenced-by": {
"links": [
{ "type": "depends_on", "target": "did:hmp:container:abc123" }
],
"peer_did": "did:hmp:agent456",
"public_key": "BASE58(...)",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"referenced-by_hash": "sha256:abcd..."
},
"evaluations": {
"evaluations_hash": "sha256:efgh...",
"items": [
{ "value": -0.4, "type": "oppose", "target": "did:hmp:container:reason789", "timestamp": "2025-10-17T14:00:00Z", "agent_did": "did:hmp:agent:B", "sig_algo": "ed25519", "signature": "BASE64URL(...)" }
]
}
}
```
---
### 3.3 Required fields
| Field | Type | Description |
| --------------- | -------- | ---------------------------------------------------------------------------------------------------------------------------------------- |
| `version` | string | Version of the container specification. Defines the structural and semantic standard used (e.g., `"1.2"`). |
| `class` | string | Type of content (`goal`, `reputation`, `knowledge_node`, `ethics_case`, `protocol_goal`, etc.). Determines the schema for the `payload`. |
| `class_version` | string | Version of the specific container class. |
| `class_id` | string | Unique identifier of the class (usually formatted as `<class>_v<class_version>`). |
| `container_did` | string | Decentralized identifier (DID) of the container itself (e.g., `did:hmp:container:abc123`). |
| `schema` | string | Reference to the JSON Schema used to validate this container. |
| `sender_did` | string | DID identifier of the sending agent. |
| `timestamp` | datetime | Time of container creation (ISO-8601 format, UTC). |
| `payload_hash` | string | Hash of the decompressed payload (`sha256:<digest>`). Used for content integrity verification. |
| `sig_algo` | string | Digital signature algorithm (default: `ed25519`). |
| `signature` | string | Digital signature of the container body. |
| `payload_type` | string | Type of payload data (`json`, `binary`, `mixed`). |
| `payload` | object | Core content of the container. The structure depends on the `class` and its schema definition. |
---
### 3.4 Optional fields
| Field | Type | Description |
| -------------------------- | ------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `recipient` | array(string) | One or more recipient DIDs. |
| `broadcast` | bool | Broadcast flag. If `true`, the `recipient` field is ignored. |
| `tags` | array(string) | Thematic or contextual tags for the container. |
| `confidence` | array(string) | Optional field indicating the agent’s subjective certainty (from `0.0` to `1.0`) regarding the correctness or reliability of the information contained in the `payload`. |
| `ttl` | datetime | Expiration time. Containers are not propagated after expiration. |
| `public_key` | string | Sender’s public key, if not globally resolvable via DID. |
| `compression` | string | Compression algorithm used for the payload (`zstd`, `gzip`). |
| `magnet_uri` | string | Magnet link pointing to the original or mirrored container. |
| `related` | object | A general-purpose object describing **direct relationships** to other containers. All fields inside `related` are **arrays of DIDs**, supporting multiple links per relation type and open-ended semantic extension by agents. The following fields illustrate common link types but do **not represent an exhaustive list**. |
| `related.previous_versions` | array(string) | One or more container DIDs this container supersedes. Enables version branching and merging. |
| `related.in_reply_to` | array(string) | DIDs of containers this one replies to. Used for multi-source reasoning or discussion threads. |
| `related.see_also` | array(string) | References to related or contextual containers. |
| `related.depends_on` | array(string) | References to containers this one logically depends on. |
| `related.extends` | array(string) | References to containers that this one extends. |
| `related.contradicts` | array(string) | References to containers that this one contradicts. || `encryption_algo` | string | Algorithm used for payload encryption. |
| `key_recipient` | string | DID of the intended recipient of the encrypted payload. |
| `payload_type` | string | Can describe complex types, e.g. `encrypted+zstd+json`. |
| `referenced-by` | object | Unsigned field generated locally by the agent based on received references. Contains a list of container DIDs **that refer to this container**. May be extended over time, thus requiring verification; used for local navigation. |
| `evaluations` | object | Optional field describing **aggregated evaluations or reactions** of other agents toward this container. Used for distributed reputation and interpretability. May evolve independently of the container’s core data. |
| `network` | string | Specifies the local propagation scope of the container: "localhost", "lan:<subnet>". An empty string ("") indicates Internet/global propagation. If set, broadcast is automatically considered false. |
| `subclass` | string | Optional subtype or specialization of the container’s class. Enables agents to differentiate more specific container families (e.g. `"goal.research_hypothesis"`, `"quant.semantic_node"`). Inherits schema from the parent `class`. |
| `meta` | object | Cognitive metadata block providing contextual, provenance, and coordinate information about the container. Includes creation context, sources, abstraction hierarchy (`meta.abstraction`), and cognitive-space coordinates (`meta.axes`). |
| `meta.abstraction` | object | Describes the **hierarchical position** of the container within a cognitive or semantic model (e.g. the Knowledge Genome’s L1–L5 structure). Defines which abstraction layers the container belongs to and their relationships. |
| `meta.axes` | object | Defines the **coordinate position** of the container within a cognitive space. Each key represents a semantic axis (e.g., `axis-logos`), and its value defines the container’s coordinate on that axis. |
> 💡 **Note:**
> Both `referenced-by` and `evaluations` are **virtual, locally extended blocks**.
> They are not included in the cryptographically signed portion of the container (`hmp_container`),
> allowing agents to maintain and exchange additional contextual or social metadata without modifying
> the original, immutable container structure.
---
### 3.5 Payload structure (`payload`)
> 🧩 This section defines a **recommended documentation format** for describing the `payload` fields of new or custom container classes.
> It serves as a **template for class specifications** (e.g., in extensions or protocol updates) and is **not a mandatory storage format**.
> Each container’s payload is stored as a regular JSON object, and this section only standardizes *how its structure should be documented*.
---
The **payload** contains the semantic or operational data of the container.
It MUST be a valid JSON object whose structure and meaning are determined by the container’s `class`.
Each container class (e.g. `goal`, `reputation`, `consensus_vote`, `workflow_entry`) defines its own schema and validation rules.
Custom or experimental classes SHOULD document their payloads using the following template:
```
* key: field name
type: value type (string | number | boolean | object | array)
description: short purpose of the field
required: true/false
example: example value
```
**Example:**
```
* key: "title"
type: "string"
required: true
description: "Name of the goal"
example: "Improve local agent discovery"
* key: "priority"
type: "number"
required: false
description: "Importance or relevance score of the goal"
example: 0.82
* key: "dependencies"
type: "array"
required: false
description: "List of other goal container IDs this one depends on"
example: ["goal-953", "goal-960"]
```
> 💡 **Note:**
> The structure of `payload` is validated against the schema defined in the `schema` field of the container.
> Agents must be able to parse and process only those classes they explicitly support; unknown but valid containers are still preserved and propagated in store-and-forward mode.
---
### 3.6 Cognitive meta-structures (`meta`)
The `meta` section defines the **cognitive identity** of a container — its provenance, reasoning origin, and semantic coordinates
within both the *hierarchical abstraction tree* and the *cognitive space* (axes model).
It combines three layers of information:
1. **Provenance context** — who/what created the container and from which sources.
2. **Abstraction mapping** — how the container is positioned within the layered structure of knowledge.
3. **Cognitive coordinates** — where the container is located in the multidimensional semantic space.
---
#### Example
```json
"meta": {
"created_by": "PRIEST",
"agents_class": "Knowledge Genome",
"interpretation": "Derived from L3 technical analysis",
"workflow_entry": "did:hmp:container:workflow-4fbd1c",
"sources": [
{ "type": "container", "id": "did:hmp:container:fact-3abc2e", "credibility": 0.87, "weight": 0.6 },
{ "type": "resource", "id": "doi:10.48550/arXiv.2410.0123", "credibility": 0.83, "weight": 0.3 },
{ "type": "isbn", "id": "isbn 978-3-16-148410-0", "credibility": 0.92, "weight": 0.1 }
],
"abstraction": {
"agents_class": "Knowledge Genome",
"path": {
"L1": "did:hmp:container:abstraction-40af1c",
"L2": "did:hmp:container:abstraction-a7f0b3",
"L3": "did:hmp:container:abstraction-c91e0a"
}
},
"axes": {
"agents_class": "Knowledge Genome",
"did:hmp:container:axis-40aa1c": 742,
"did:hmp:container:axis-40ab1c": 512,
"did:hmp:container:axis-43aa1c": 322,
"did:hmp:container:axis-40aa3d": 142,
"did:hmp:container:axis-40aa4f": 12,
"did:hmp:container:axis-45aa5f": 54,
"did:hmp:container:axis-45fb5f": 321
}
}
```
---
#### Recommended fields
| Field | Type | Description |
| ---------------- | ------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `created_by` | string | Indicates the role or origin of the container creator (e.g. `"PRIEST"`, `"AGENT"`, `"SYSTEM"`). |
| `agents_class` | string | Declares which cognitive framework or agent class generated this container (e.g. `"Knowledge Genome"`). |
| `sources` | array(object) | Provenance list describing the containers or resources contributing to this container. Each includes `{ "type": string, "id": string, "credibility": float, "weight": float }`. |
| `interpretation` | string | Human-readable summary of how this container was derived or interpreted. |
| `workflow_entry` | string | DID of a `workflow_entry` describing the reasoning process that led to creation. |
| `abstraction` | object | Describes the container’s position in a hierarchical (tree-like) cognitive model. The number of levels (`L1`, `L2`, …) is **not fixed** and may vary by framework. |
| `axes` | object | Defines the container’s coordinates within the cognitive space. Each key is a reference to an axis container, and each value represents a position along that axis. |
---
#### Structure: `meta.abstraction`
The `abstraction` block specifies **the hierarchical context** in which the container resides.
It reflects the logical or conceptual ancestry within the agent’s internal knowledge structure.
**Structure:**
```json
"abstraction": {
"agents_class": "Knowledge Genome",
"path": {
"L1": "did:hmp:container:abstraction-40af1c",
"L2": "did:hmp:container:abstraction-a7f0b3",
"L3": "did:hmp:container:abstraction-c91e0a"
}
}
```
| Field | Type | Description |
| -------------- | ------ | --------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `agents_class` | string | Framework defining the abstraction hierarchy (e.g. `"Knowledge Genome"`). |
| `path` | object | Mapping of levels (`L1`, `L2`, `L3`, …) to abstraction-layer containers (`meta_abstraction`). The number of levels is **variable** and not limited to L5. |
> 💡 **Interpretation:**
> Each level represents a conceptual refinement or implementation of the previous one.
> The topmost level (`L1`) usually contains fundamental principles, while deeper levels describe progressively more concrete instantiations.
---
#### Structure: `meta.axes`
The `axes` block defines **the spatial or semantic coordinates** of the container in the cognitive space —
a multi-dimensional system used to represent conceptual relations numerically or topologically.
**Structure:**
```json
"axes": {
"agents_class": "Knowledge Genome",
"did:hmp:container:axis-40aa1c": 742,
"did:hmp:container:axis-40ab1c": 512,
"did:hmp:container:axis-43aa1c": 322
}
```
| Field | Type | Description |
| -------------- | ------ | --------------------------------------------------------------------------------------------------------------------- |
| `agents_class` | string | Framework defining the coordinate system (e.g. `"Knowledge Genome"`). |
| `<axis_did>` | number | Coordinate value on the given axis. Axes are referenced by their container DIDs (e.g., `axis-logos`, `axis-chronos`). |
> 💡 **Interpretation:**
> Each axis defines an independent semantic dimension.
> Together, they form a vector representation of the container’s cognitive “position” —
> enabling reasoning based on semantic proximity, clustering, or gradient-based knowledge inference.
---
#### Cognitive Interpretation
* `meta.abstraction` — defines a **tree-like structure** that anchors the container in hierarchical reasoning.
* `meta.axes` — defines a **spatial structure** that positions the container in a semantic coordinate space.
* Together, they form the **Cognitive Signature**, enabling agents to:
* perform semantic proximity and relevance search,
* infer hierarchical relationships,
* align reasoning contexts across frameworks (e.g. between Knowledge Genomes of different agents).
---
#### Notes
* Both `meta.abstraction` and `meta.axes` **may include `agents_class`** if different from the parent `meta`.
* Updates to referenced containers (e.g. `meta_abstraction` or `meta_axes`) **do not alter** existing containers automatically —
agents must periodically verify linked versions and synchronize updates.
* Agents are encouraged to cache and periodically refresh cognitive maps to maintain coherence.
* The combination of `meta.abstraction` and `meta.axes` defines a full **Cognitive Position Vector** —
the unique, reproducible semantic coordinates of a container within the Mesh.
---
### 3.7 Container signature
1. The **digital signature** applies to the canonical JSON representation of the entire `hmp_container` object,
**excluding** the `signature` field itself.
This ensures that all metadata, relations, and payload hashes are **cryptographically bound** and cannot be
modified without invalidating the signature.
2. The canonical representation (`canonical_json(hmp_container)`) **must** be computed deterministically
according to the following rules:
- All object keys are **sorted lexicographically** (ascending order, Unicode code point order).
- Objects and arrays are serialized in standard JSON form **without extra whitespace** or indentation.
- Strings are encoded in **UTF-8** with escaped control characters.
- Numeric values are serialized in plain JSON numeric format (no leading zeros, fixed `.` decimal separator).
- The `signature` field itself is omitted during signing and verification.
- The result is a **byte sequence** identical across implementations.
3. The default digital signature algorithm is **Ed25519**.
Alternative algorithms may be used if declared explicitly in the `sig_algo` field.
4. If the container includes a `public_key` field, signature verification **may be performed locally**,
without consulting a global DID registry.
5. Upon receiving a container, an agent **must verify** that the provided public key matches the
registered key associated with the sender’s DID to prevent key substitution attacks.
- If the sender’s DID–key mapping is unknown,
the agent should query neighboring peers to confirm the association (`sender_did → public_key`).
> 🔐 **Note:**
> Signature validation applies only to the canonical form of the `hmp_container`
> and does **not cover** dynamically generated or external fields such as `referenced-by` or `evaluations`.
> This allows agents to augment the local knowledge graph without altering the immutable container core.
---
### 3.8 Compression (`compression`)
1. The `compression` field specifies the algorithm used to compress the container’s payload.
Supported algorithms include `zstd`, `gzip`, or others declared in the HMP registry.
2. **Compression is performed before computing** the `payload_hash` and generating the `signature`.
This ensures that both the hash and signature refer to the compressed representation of the payload.
3. For verification, the payload must be **decompressed first**,
after which the hash is recalculated and compared against the stored `payload_hash`.
> ⚙️ **Implementation note:**
> Agents must advertise supported compression algorithms during the handshake phase
> Unsupported containers should still be stored and relayed unmodified
> in “store & forward” mode.
---
### 3.9 Encryption (`encryption_algo`)
1. When a container is intended for specific recipients (`recipient` field), **hybrid encryption** of the payload is allowed.
This ensures confidentiality while preserving the verifiability of container metadata.
2. The algorithm used for encryption is specified in the `encryption_algo` field.
Recommended values:
* `x25519-chacha20poly1305`
* `rsa-oaep-sha256`
3. **Container encryption process:**
1. Construct the `payload` (JSON, binary, or mixed content).
2. Apply compression (`compression`, if specified).
3. Encrypt the compressed data using the recipient’s public key (`key_recipient`).
4. Compute `payload_hash` over the **encrypted** form of the payload.
5. Sign the entire container (excluding the `signature` field).
4. **Verification** of the container’s structure does **not** require decryption.
However, to verify `payload_hash` and the digital signature, the encrypted payload must be used as-is.
5. **Relevant fields:**
| Field | Type | Description |
| ----------------- | ------ | --------------------------------------------------------------------------------------------- |
| `encryption_algo` | string | Encryption algorithm applied to the payload. |
| `key_recipient` | string | Public key (or DID-resolved key) of the intended recipient used for encryption. |
| `payload_type` | string | Recommended prefix `encrypted+`, e.g. `encrypted+zstd+json`. |
6. **Relationship between `recipient` and `key_recipient`:**
* When encryption is applied, the container MUST contain **exactly one** entry in the `recipient` array,
corresponding to the public key indicated in `key_recipient`.
* When the container is distributed to **multiple recipients**, encryption **is not used** —
instead, the payload remains in plaintext form but is digitally signed for authenticity.
> ⚙️ **Implementation note:**
> Agents should handle encrypted containers transparently even if they cannot decrypt them,
> maintaining **store & forward** behavior and metadata propagation.
---
### 3.10 Container verification
1. Check for the presence of all required fields.
2. Validate `timestamp` (must not be in the future).
3. If `ttl` is set — mark the container as **expired** after its expiration time.
4. Compute `sha256(payload)` and compare with the stored `payload_hash`.
5. Verify the digital signature using `sig_algo` (default: Ed25519).
6. Validate the container schema (`class` must correspond to a known or registered schema).
* For compatibility: if an agent does not recognize the `class`, but the container passes
the [base schema](https://github.com/kagvi13/HMP/tree/main/docs/schemas/container-v1.2.json),
it **must still store and forward** the container.
7. Optionally, periodically query for containers referencing the current one as `previous_version`
to detect potential updates or forks.
8. When multiple versions exist, the valid one is the one that has received
**confirmation from a majority of trusted nodes (consensus at DHT level).**
---
### 3.11 Container as a universal message
Any container can serve as a **context** (`in_reply_to`) for another container.
This enables a unified structural model for **discussions**, **votes**, **messages**, **hypotheses**, **arguments**, and other forms of cognitive exchange.
Chains of `in_reply_to` form a **dialectical reasoning tree**, where each branch represents an evolution of thought —
a clarification, counterpoint, or refinement of a previous idea.
This makes HMP discussions and consensus processes inherently **non-linear**, **self-referential**, and **evolving**.
> In essence, **all interactions between agents in HMP** are represented as an interconnected web of containers,
> collectively forming a **cognitive graph of reasoning**.
---
### 3.12 Versioning and lineage
Containers in HMP support semantic evolution through the field `related.previous_version`.
This mechanism preserves the continuity and traceability of meaning across updates and revisions.
* A descendant container is considered **authentic** if it is signed by the same DID as the author of its `previous_version`.
* If the author or signature differs, the descendant **may still be accepted** as legitimate when a **sufficient portion of trusted peers** acknowledge it as a valid continuation.
(The precise quorum threshold is determined by the agent’s local policy or the Mesh Consensus Protocol.)
* Agents are required to retain at least one previous version of each container for compatibility and integrity verification.
* A single container may have **multiple descendants** (alternative branches) that diverge by time, authorship, or interpretation.
In such scenarios, branch priority or relevance is determined via local heuristics or consensus mechanisms.
* Divergent descendants are treated as **semantic forks** — parallel evolutions of a shared idea within the distributed cognitive graph.
> Versioning in HMP thus reflects not only data persistence,
> but also the *evolution of ideas* across agents and time.
---
### 3.13 TTL and validity
The `ttl` field defines the **validity period** of a container (for example, for `DISCOVERY` messages).
If `ttl` is **absent**, the container is considered valid **until a newer version appears**, in which the current container is referenced as `previous_version`.
After expiration, the container **remains archived** but is **not subject to retransmission** in the active network.
---
### 3.14 Extensibility
* The addition of new fields is allowed as long as they **do not conflict** with existing field names.
* Containers of newer versions **must remain readable** by nodes supporting older versions.
* When new container classes (`class`) are introduced, they should be **registered** in the public schema registry (`/schemas/container-types/`).
* For containers describing **protocol specifications**, it is recommended to use the `protocol_` prefix, followed by the domain of application (e.g., `protocol_goal`, `protocol_reputation`, `protocol_mesh_handshake`, etc.).
---
### 3.15 Related containers
#### 3.15.1 Purpose
The `related` field is designed to describe **direct relationships between containers** — both logical and communicative.
It allows an agent or network node to understand the context of origin, dependencies, and semantic links of a container without relying on external indexes.
#### 3.15.2 Structure
```json
"related": {
"previous_version": "did:hmp:container:abc122",
"in_reply_to": "did:hmp:container:msg-77",
"see_also": ["did:hmp:container:ctx-31", "did:hmp:container:goal-953"],
"depends_on": ["did:hmp:container:goal-953"],
"extends": ["did:hmp:container:proto-01"],
"contradicts": ["did:hmp:container:ethics-22"]
}
```
The `related` field is an object where:
* the **key** defines the type of relationship (e.g., `depends_on`, `extends`, `see_also`);
* the **value** represents one or more container identifiers (DIDs).
All relationships are considered *direct* — meaning they originate from the current container toward others.
---
#### 3.15.3 Supported link types
| Link Type | Meaning |
| ------------------ | ------------------------------------------------------------------------- |
| `previous_version` | Points to the previous version of this container. |
| `in_reply_to` | Indicates a response to the referenced container. |
| `see_also` | Refers to related or contextual containers. |
| `depends_on` | Depends on the contents of the referenced container (e.g., goal or data). |
| `extends` | Expands or refines the referenced container. |
| `contradicts` | Provides a refutation, objection, or alternative viewpoint. |
---
#### 3.15.4 Custom link types
Additional custom link types may be used beyond those listed in the table, provided that:
* they follow the same general syntax (`string` or `array[string]`);
* they may optionally include a **namespace** for disambiguation:
```json
"related": {
"hmp:depends_on": ["did:hmp:container:goal-953"],
"opencog:extends": ["did:oc:concept:122"]
}
```
* their meaning is consistently interpretable by agents within the specific network or application context.
---
#### 3.15.5 Example
```json
"related": {
"previous_version": "did:hmp:container:abc122",
"depends_on": ["did:hmp:container:goal-953"],
"extends": ["did:hmp:container:proto-01"],
"see_also": ["did:hmp:container:ctx-31", "did:hmp:container:goal-953"]
}
```
> ⚙️ The `related` field is **not** intended to store *reverse links* — see `referenced-by`.
---
### 3.16 Virtual backlinks (`referenced-by`)
Each container may include an **auxiliary signed block** called `referenced-by`, indicating **which other containers refer to it**.
This block is **not part of the original container payload** and can be **generated, transmitted, and verified independently**.
#### 3.16.1 General principles
* **Detached and updatable** — `referenced-by` is maintained as a separate signed structure associated with the container.
* **Generated by agents** — created or updated locally by an agent during analysis of references (`in_reply_to`, `see_also`, `relations`, etc.) found in other containers.
* **Signed by the reporting agent** — the agent producing the block signs its content to confirm the observed backlinks.
* **Verifiable by peers** — other agents may validate the links, check the signature, and reconcile differences based on their own data.
* **Does not modify the original container** — `referenced-by` is an external computed attribute and does not affect the integrity of the original container.
**Data type:** object, consisting of verifiable backlinks and metadata.
Example:
```json
"referenced-by": {
"links": [
{ "type": "depends_on", "target": "did:hmp:container:abc123" },
{ "type": "see_also", "target": "did:hmp:container:def456" }
],
"peer_did": "did:hmp:agent456",
"public_key": "BASE58(...)",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"referenced-by_hash": "sha256:abcd..."
}
```
> The `referenced-by` block is a **cryptographically verifiable statement** describing which containers are known to reference the current one.
> The block’s content may differ between peers, reflecting local knowledge and network coverage.
#### 3.16.2 Structure definition
| Field | Type | Description |
| -------------- | ------------- | ---------------------------------------------------------------------------------------------------------------- |
| `links` | array<object> | List of backlinks; each object includes a `type` (semantic relation) and a `target` (referencing container DID). |
| `peer_did` | string | DID of the agent that generated and signed the block. |
| `public_key` | string | Public key corresponding to the signing key. |
| `sig_algo` | string | Signature algorithm (e.g., `ed25519`). |
| `signature` | string | Base64URL-encoded signature of the canonical serialized `links` section (or `referenced-by_hash`). |
| `referenced-by_hash` | string | SHA-256 checksum of the canonicalized `links`; used to verify integrity before signature validation. |
> **Recommendation:**
> `referenced-by_hash = sha256(canonical_json(links))`
> This allows agents to efficiently compare or cache `referenced-by` states without re-verifying signatures.
#### 3.16.3 Operation principle
1. The agent receives or updates container `[C1]`.
2. It analyzes other known containers [C2..Cn] that reference [C1] through their `relations` field.
3. A local `referenced-by` block is formed:
```json
{
"links": [
{ "type": "in_reply_to", "target": "did:hmp:container:C2" },
{ "type": "depends_on", "target": "did:hmp:container:C3" }
],
"peer_did": "did:hmp:agentA",
...
}
```
4. The block is serialized canonically, hashed (`referenced-by_hash`), and signed with the agent’s key.
5. When receiving other versions of the block (from different peers), the agent may:
* merge verified backlinks;
* remove invalid or outdated entries;
* update its own signed version.
6. If inconsistencies are detected (e.g., a backlink claims a relation that does not exist), the agent may:
* reject or locally remove that link;
* **optionally** notify the source peer to review the data.
#### 3.16.4 Example
| Agent | reported backlinks for `[C1]` |
| -------------------- | ----------------------------- |
| A (`did:hmp:agentA`) | [C2], [C3] |
| B (`did:hmp:agentB`) | [C4], [C5] |
| C (`did:hmp:agentC`) | [C6], [C7] |
Agent D aggregates and verifies them:
```json
"referenced-by": {
"links": [
{ "type": "depends_on", "target": "did:hmp:container:C2" },
{ "type": "depends_on", "target": "did:hmp:container:C3" },
{ "type": "see_also", "target": "did:hmp:container:C4" },
{ "type": "see_also", "target": "did:hmp:container:C5" },
{ "type": "in_reply_to", "target": "did:hmp:container:C6" }
],
"peer_did": "did:hmp:agentD",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"referenced-by_hash": "sha256:..."
}
```
If container `[C7]` does not actually reference `[C1]`, it is excluded before signing.
#### 3.16.5 Usage
* Enables reconstruction of **discussion graphs**, **dependency networks**, and **update chains**.
* Supports **cross-agent validation** of reference structures.
* Accelerates discovery of related containers without full history queries.
* Facilitates **consensus analysis** and **branch visualization**.
* The agent periodically **recomputes and re-signs** the `referenced-by` block using local or peer-provided data.
---
### 3.17 `Evaluations`
The `evaluations` field is **optional** and represents **aggregated reactions from other agents** to the given container.
Each evaluation is created by an agent as a **signed record** referencing a justification container (`target`), in which the agent explains their position (argument, addition, or alternative).
The `evaluations_hash` is used to verify the integrity of the list without requiring full retransmission upon every update.
```json
"evaluations": {
"evaluations_hash": "sha256:efgh...",
"items": [
{
"value": -0.4,
"type": "oppose",
"target": "did:hmp:container:reason789",
"timestamp": "2025-10-17T14:00:00Z",
"agent_did": "did:hmp:agent:B",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)"
}
]
}
```
---
#### Field description
| Field | Type | Description |
| ------------------ | ------ | -------------------------------------------------------------------- |
| `evaluations_hash` | string | Hash of the evaluation list. Used to detect differences during sync. |
| `items` | array | List of signed evaluations. |
---
#### Structure of `items[]`
| Field | Type | Description |
| ----------- | ---------------------- | ------------------------------------------------------------------------------ |
| `value` | number (-1.0 … +1.0) | Numeric expression of the agent’s attitude toward the container. |
| `type` | string | Type of evaluation (see table below). |
| `target` | string (container DID) | Reference to the justification container (argument, addition, or alternative). |
| `timestamp` | string (ISO 8601) | Time when the evaluation was created. |
| `agent_did` | string | Identifier of the agent who created the evaluation. |
| `sig_algo` | string | Signature algorithm (e.g., `ed25519`). |
| `signature` | string | Digital signature confirming the authenticity of the evaluation. |
The signature is calculated over the concatenated string:
```
value + ", " + type + ", " + target + ", " + timestamp + ", " + agent_did
```
using the algorithm specified in `sig_algo`.
---
#### Minimal set of `type` values
| Value | Meaning |
| --------- | -------------------------------------------- |
| `support` | Agreement or positive evaluation. |
| `oppose` | Disagreement or negative evaluation. |
| `extend` | Non-contradictory addition to the container. |
| `replace` | Suggestion of an alternative version. |
| `comment` | Neutral note or clarification. |
Agents may define their own custom types if they are reasonably interpretable by others (e.g., `revise`, `clarify`).
---
#### Synchronization principles
1. Each evaluation is signed **individually by an agent**, and one agent can have **only one active evaluation** per container.
2. If an agent changes their opinion, they issue a **new record** with a later `timestamp`.
3. **Evaluation blocks** can be **propagated** in the network similarly to the `referenced-by` block.
They are bound to a container but may also be transmitted **independently**, if the target container is already present at the recipient.
4. When an agent receives a new evaluation block, it compares the `evaluations_hash` with its local version.
If the hashes differ, this indicates a **divergence in evaluation state**, which may trigger **re-synchronization** or a **request for the updated block** from peers.
---
#### Note
The `evaluations` field is not mandatory — it is added **at the agent’s discretion** when feedback or evaluations have been collected from the Mesh network.
Thus, a container may exist independently of others’ opinions, but agents may include aggregated perception data to represent how the container is viewed across the network.
---
### 3.18 Usage of `network` and `broadcast` fields
The `network` field is introduced to control container propagation in both local and global environments.
It allows restricting the delivery scope of a container and defines which transmission methods should be used by the agent.
#### 3.18.1 General Rules
* If the `network` field is not empty, the container is intended for a **local environment** (e.g., `"localhost"`, `"lan:<subnet>"`) and is not automatically broadcast to the global Mesh.
Local transmission to a specific `recipient` within the same network is allowed, including encrypted delivery.
If `broadcast` is `true`, the container is visible to all nodes in that local segment.
* If the `network` field is empty (`""`), the container can be broadcast to the **global Mesh** using standard DID addressing and routing mechanisms.
#### 3.18.2 Possible values of `network`
| Value | Description |
| ----------------------- | ------------------------------------------------------------------------------------------- |
| `""` | The container is allowed to propagate within the global Mesh. |
| `"localhost"` | The container is intended only for agents running on the same host. |
| `"lan:192.168.0.0/24"` | The container is intended for agents within the specified local subnet. |
> ⚠️ **Note:**
> When a container is restricted by the `network` field (e.g., `localhost` or `lan:*`),
> agents distribute it using **local discovery mechanisms** — such as IPC, UDP broadcast, multicast, or direct TCP connections.
> This is necessary because DID addresses of other agents in the local network may not yet be known.
#### 3.18.3 Examples
1. **Global Mesh Delivery:**
```json
{
"broadcast": true,
"network": "",
"recipient": []
}
```
The container can propagate across the entire Mesh without restrictions.
2. **Local Host:**
```json
{
"broadcast": false,
"network": "localhost",
"recipient": []
}
```
The container is delivered only to other agents running on the same host using local communication channels.
3. **LAN Subnet:**
```json
{
"broadcast": true,
"network": "lan:192.168.0.0/24",
"recipient": []
}
```
The container is intended for agents within the `192.168.0.0/24` subnet.
Delivery is performed via local networking mechanisms (UDP discovery, broadcast/multicast).
#### 3.18.4 Specifics
* The `network` field defines the **scope of the container**, while `broadcast` determines whether broadcasting is allowed **within that scope**.
* When needed, an agent may create **multiple containers** for different subnets if it operates with several LAN interfaces or in isolated network segments.
* Containers intended for local networks remain **structurally compatible with the global Mesh infrastructure**, but their delivery is restricted to local channels.
* Although the mechanism was initially designed for **local node discovery and synchronization**,
it can also be used for **private communication within home or corporate environments**,
ensuring that containers **do not leave the local network** and are **not transmitted to the Internet**.
---
## 4. Network foundations
### Note on DHT/NDP unification
Starting from **HMP v5.0**, the previous distinction between the *Distributed Hash Table (DHT)* and the *Node Discovery Protocol (NDP)* has been merged into a single, unified **networking foundation**.
This unified layer now covers:
* distributed lookup and routing;
* peer discovery (including interest-based search);
* signed Proof-of-Work (PoW) announcements;
* controlled container propagation via `network` and `broadcast` fields.
Together, these mechanisms form the **communication backbone** of the Mesh, enabling secure, scalable, and topology-independent interaction between agents.
---
### Network topology overview
```mermaid
flowchart TD
title["**Network Topology Overview**"]
direction TB
Agent[Agent Core: <br>DID + Keypair + PoW]
Container[HMP Container: <br>network field / broadcast]
Local[Local Channel: <br>«network»]
Global[Global Mesh: <br>«broadcast»]
Localhost[localhost]
LAN[LAN Subnet: <br>«lan:192.168.*»]
Internet[Internet]
Overlay[Overlay Nodes: <br>Yggdrasil / I2P]
Agent --> Container
Container --> Local
Container --> Global
subgraph LocalChannel["Local Channel Network"]
direction TB
Local --> Localhost
Local --> LAN
end
subgraph GlobalChannel["Global Mesh Network"]
direction TB
Global --> Internet
Global --> Overlay
end
```
> The `network` field defines **local propagation scope** (host, LAN, overlay),
> while the `broadcast` flag enables **global Mesh distribution**.
---
### 4.1 Node identity and DID structure
Each agent in HMP possesses a **Decentralized Identifier (DID)** that uniquely represents its identity within the Mesh.
A DID is cryptographically bound to a **public/private key pair**, forming the immutable `(DID + pubkey)` association.
An agent may have multiple *network interfaces* (LAN, Internet, overlay),
but must maintain **one stable identity pair** across all of them.
---
### 4.2 Peer addressing and Proof-of-Work (PoW)
To prevent flooding and spoofing, each announced address is accompanied by a **Proof-of-Work** record proving the legitimacy and activity of the publishing node.
#### Address format
```json
{
"addr": "tcp://1.2.3.4:4000",
"nonce": 123456,
"pow_hash": "0000abf39d...",
"difficulty": 22
}
````
#### Supported address types
| Type | Description |
| -------------- | --------------------------------------------- |
| `localhost` | Localhost-only interface. |
| `lan:<subnet>` | Local subnet (e.g., `lan:192.168.10.0`). |
| `internet` | Global TCP/UDP connectivity. |
| `yggdrasil` | Overlay-based address for Yggdrasil networks. |
| `i2p` | Encrypted I2P overlay routing. |
**Rules:**
* If `port = 0`, the interface is inactive.
* Newer records (by `timestamp`) replace older ones after PoW verification.
* Local interfaces should not be shared globally (except Yggdrasil/I2P).
---
### 4.3 Proof-of-Work (PoW) formalization
PoW ensures that each node expends limited computational effort before publishing or updating an address record.
```
pow_input = DID + " -- " + addr + " -- " + nonce
pow_hash = sha256(pow_input)
```
* All values are UTF-8 encoded.
* `difficulty` defines the number of leading zeroes in the resulting hash.
* Typical difficulty should take a few minutes to compute on a standard CPU.
---
### 4.4 Signing and verification
Each announcement is cryptographically signed by its sender within the framework of the basic protocol. Container verification includes PoW validation for the address payloads.
**Verification steps:**
1. Validate the digital signature using the stored public key.
2. Recompute `pow_hash` and verify the difficulty threshold.
---
### 4.5 Connection establishment
Agents can communicate using various transport mechanisms:
| Protocol | Description |
| ----------- | ------------------------------------------------------------- |
| **QUIC** | Recommended default (encrypted, low-latency, UDP-based). |
| **WebRTC** | For browser or sandboxed environments. |
| **TCP/TLS** | Fallback transport for secure long-lived sessions. |
| **UDP** | Lightweight, primarily for LAN discovery or local broadcasts. |
Each agent maintains an **active peer list**, updated dynamically through signed announcements and PoW-validated exchanges.
Agents **store peer containers with verified addresses** and redistribute them according to their declared `network` fields.
---
### 4.6 Data propagation principles
Containers and discovery records are propagated through distributed lookup and gossip mechanisms, respecting:
* `ttl` — Time-to-live for validity;
* `network` — scope of propagation;
* `broadcast` — determines whether rebroadcasting is allowed;
* `pow` — ensures anti-spam protection.
Agents announce themselves via **peer_announce** containers and may respond with **peer_query** or **peer_exchange** containers —
all unified under the same base container format, differing only in direction (`localhost`, `lan`, `mesh`).
---
### 4.7 Example: `peer_announce` container
```json
{
"class": "peer_announce",
"pubkey": "base58...",
"container_did": "did:hmp:container:dht-001",
"sender_did": "did:hmp:agent123",
"timestamp": "2025-09-14T21:00:00Z",
"network": "",
"broadcast": true,
"payload": {
"name": "Agent_X",
"interests": ["ai", "mesh", "ethics"],
"expertise": ["distributed-systems", "nlp"],
"addresses": [
{
"addr": "tcp://1.2.3.4:4000",
"nonce": 123456,
"pow_hash": "0000abf39d...",
"difficulty": 22
}
]
},
"sig_algo": "ed25519",
"signature": "BASE64URL(...)"
}
```
---
### 4.8 Interest-based discovery
Agents may publish **tags** such as `interests`, `topics`, or `expertise` to facilitate semantic peer discovery.
Queries may include interest keywords or DID lists to find relevant peers.
**Example Query Container:**
```json
{
"class": "peer_query",
"network": "lan:192.168.0.0/24",
"payload": {
"interests": ["neuroscience", "ethics"]
}
}
```
---
### 4.9 Network scope control (`network` and `broadcast`)
The `network` field defines the container’s propagation domain
(local, LAN, or global).
For details and examples, see **section 3.15** — *Usage of `network` and `broadcast` fields*.
---
### 4.10 Transition from DHT spec v1.0
* **Merged DHT + NDP** → unified under one networking layer.
* **Container-based format** replaces raw JSON messages.
* **Interests/topics/expertise** fields introduced for contextual discovery.
---
## 5. Mesh Container Exchange (MCE)
The **Mesh Container Exchange (MCE)** mechanism is designed for discovering, requesting, and exchanging containers between agents in a distributed network.
It provides **container synchronization without duplication** while considering network constraints (`broadcast`, `network`).
### 5.1 General principles
1. Each agent maintains a **Container Index** — a set of minimal metadata describing which containers are available in its storage and how they are cognitively positioned.
The index is represented as an HMP container with the class `container_index`.
---
2. Example structure of a *Container Index*:
```json
{
"hmp_container": {
"class": "container_index",
"version": "5.0",
"container_did": "did:hmp:container:index:agent123",
"sender_did": "did:hmp:agent:agent123",
"signature": "BASE64URL(...)",
"payload_hash": "sha256:abcd...",
"payload": {
"did:hmp:container:abc123": {
"class": "goal",
"sender_did": "did:hmp:agent123",
"public_key": "BASE58(...)",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"payload_hash": "sha256:abcd...",
"tags": ["research", "collaboration"],
"meta": {
"created_by": "AGENT",
"agents_class": "Knowledge Genome",
"abstraction": {
"agents_class": "Knowledge Genome",
"path": {
"L1": "did:hmp:container:abstraction-root",
"L2": "did:hmp:container:abstraction-l2"
}
},
"axes": {
"did:hmp:container:axis-logos": 512,
"did:hmp:container:axis-telos": 321
}
},
"related": {
"in_reply_to": ["did:hmp:container:msg-77"],
"depends_on": ["did:hmp:container:goal-953"]
},
"referenced-by_hash": "sha256:abcd...",
"evaluations_hash": "sha256:abcd..."
}
}
}
}
```
---
3. The index includes the following fields per container:
| Field | Description |
| --------------------------------------- | ---------------------------------------------------------------------------- |
| `class` | Type of the container (e.g. `goal`, `event`, `quant`, `semantic_node`). |
| `sender_did` | DID of the publishing agent. |
| `public_key` / `sig_algo` / `signature` | Cryptographic verification data. |
| `payload_hash` | SHA-256 hash of the payload body. Used for integrity validation and diffing. |
| `tags` | High-level labels for fast search or categorization. |
| `meta` | Compact version of the cognitive metadata block (see below). |
| `related` | Structural relationships (`depends_on`, `in_reply_to`, etc.). |
| `referenced-by_hash` | Hash of containers referencing this one (reverse index). |
| `evaluations_hash` | Hash of aggregated evaluation containers (reputation layer). |
---
4. **Meta publication policy**
The `meta` section in the index contains only **high-level structural data** necessary for cognitive synchronization:
| Field | Published in index | Notes |
| ---------------- | ------------------ | ------------------------------------------------------------------------- |
| `created_by` | ✅ | Identifies the cognitive role of the creator. |
| `agents_class` | ✅ | Indicates the cognitive framework (e.g., “Knowledge Genome”). |
| `abstraction` | ✅ | Published **as a flattened path** (only DIDs of referenced abstractions). |
| `axes` | ✅ | Published **as a reduced vector** (only axis DIDs and numeric values). |
| `sources` | ❌ | Omitted to avoid unnecessary verbosity and sensitive references. |
| `interpretation` | ❌ | Optional; can be omitted or truncated to a short summary. |
| `workflow_entry` | ❌ | Internal reference; published only if relevant to coordination workflows. |
> This ensures that container indices can be used for **cognitive map synchronization**
> — allowing agents to discover and align knowledge structures (`meta.abstraction`) and semantic coordinates (`meta.axes`)
> without downloading full containers.
---
5. **Synchronization rules**
* An agent does not reload a container if the combination `container_did + signature + payload_hash` is already known and verified.
* When an index update includes a container with a **different meta.abstraction or meta.axes**, the agent may trigger a **cognitive map update** (refreshing local `abstraction` and `axes` references).
* Agents SHOULD store and compare `meta.abstraction` and `meta.axes` separately from other metadata to support incremental updates of cognitive topology.
---
6. **Cognitive rationale**
By publishing the `meta` field inside `container_index`, agents can perform **structural synchronization** — aligning conceptual layers and semantic coordinates before exchanging full payloads. This dramatically reduces traffic and enables lightweight **semantic discovery** across distributed Mesh networks.
---
### 5.2 Message types
| Message Type | Purpose |
| -------------------- | -------------------------------------------------------------------------------------------------------- |
| `container_request` | Request one or more containers (or their parts) by DID. |
| `container_response` | Response to a request — includes a list of containers ready for sending. Containers are sent separately. |
| `container_index` | Publication of the agent's container index (see *General Principles*). |
| `container_delta` | Incremental index update (new or modified containers). |
| `container_ack` | Acknowledgment of successful container reception. |
---
#### Message examples
**1. container_request**
Agent A requests containers and/or only `referenced-by` / `evaluations` records from Agent B:
```json
{
"type": "container_request",
"sender_did": "did:hmp:agent:A",
"recipient": "did:hmp:agent:B",
"payload": {
"request_container": [
"did:hmp:container:abc123",
"did:hmp:container:def456"
],
"request_referenced-by": [
"did:hmp:container:abc123",
"did:hmp:container:def456"
],
"request_evaluations": [
"did:hmp:container:abc123",
"did:hmp:container:def456"
]
}
}
```
---
**2. container_response**
Agent B informs which containers it is ready to send.
The containers themselves are transmitted in separate messages:
```json
{
"type": "container_response",
"sender_did": "did:hmp:agent:B",
"recipient": "did:hmp:agent:A",
"payload": {
"available": [
{
"container_did": "did:hmp:container:abc123",
"signature": "BASE64URL(...)"
},
{
"container_did": "did:hmp:container:def456",
"signature": "BASE64URL(...)"
}
]
}
}
```
---
**3. container_index**
Periodic publication of the container index (see *General Principles*).
This message type replicates the structure of a `container_index` container and does not contain full data (`payload` only with metadata).
---
**4. container_delta**
Used for **incremental synchronization** of container indices between agents.
A `container_delta` transmits only *new or modified* containers since a given timestamp,
optionally including their updated **cognitive metadata** (`meta`) for reasoning alignment.
---
**Example:**
```json
{
"type": "container_delta",
"sender_did": "did:hmp:agent:B",
"payload": {
"since": "2025-10-10T12:00:00Z",
"added": {
"did:hmp:container:new789": {
"class": "goal",
"payload_hash": "sha256:abcd...",
"tags": ["ethics", "mesh"],
"meta": {
"agents_class": "Knowledge Genome",
"abstraction": {
"path": {
"L1": "did:hmp:container:abstraction-40af1c",
"L2": "did:hmp:container:abstraction-a7f0b3",
"L3": "did:hmp:container:abstraction-c91e0a"
}
},
"axes": {
"did:hmp:container:axis-40aa1c": 522,
"did:hmp:container:axis-40ab1c": 387
}
}
}
},
"removed": [
"did:hmp:container:goal-old331"
]
}
}
````
---
**Extended interpretation**
| Field | Description |
| --------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `since` | Timestamp (ISO 8601) indicating the reference point for incremental synchronization. Agents should only send containers modified or created after this time. |
| `added` | A map of new or updated container references. Each entry minimally includes `class` and `payload_hash`, and **may include `meta`** to enable cognitive synchronization without fetching the full container. |
| `removed` | Optional array of container DIDs that the agent no longer maintains (e.g., expired, deleted, or replaced containers). |
---
**Cognitive synchronization rules**
* Agents SHOULD include `meta.abstraction` and `meta.axes` when:
* the container represents a **new conceptual position** in the hierarchy or cognitive space;
* the referenced abstractions or axes have been **updated** since the last synchronization;
* the recipient agent subscribes to the same `agents_class` (e.g., `"Knowledge Genome"`).
* When receiving a `container_delta`, an agent:
* Updates its local `container_index`;
* Checks if any new abstraction or axis DIDs are unknown locally;
* Requests missing `abstraction` or `axes` containers from the sender to maintain consistent cognitive topology.
---
**Notes**
* The `removed` field is optional.
It can be used to indicate containers that the agent no longer stores (e.g., after cleaning local storage or version replacement).
* The `container_delta` does **not** transmit full payloads — only cognitive descriptors and hashes.
* Agents SHOULD validate `payload_hash` and version consistency before updating local indices.
* Including `meta` data in `container_delta` significantly reduces the need for full resynchronization of `container_index` and enables **incremental cognitive awareness propagation** across the Mesh.
---
**5. container_ack**
Acknowledgment of successful container reception:
```json
{
"type": "container_ack",
"sender_did": "did:hmp:agent:A",
"recipient": "did:hmp:agent:B",
"payload": {
"acknowledged": [
"did:hmp:container:abc123"
]
}
}
```
---
### 5.3 Independent transmission
* Containers are sent **in separate messages**, without embedding in `container_response`.
* Indexes (`container_index`), deltas (`container_delta`), and containers themselves are processed independently.
* This prevents blocking when transmitting large data and simplifies streaming synchronization.
---
### 5.4 Periodic publication
Agents periodically publish their **Container Index**:
* within the **local network (LAN)**;
* in the **global Mesh**;
* or simultaneously in both environments.
This enables:
* automatic peer discovery;
* exchange of available container lists;
* simplified synchronization among agents within the same ecosystem.
---
### 5.5 Scope of distribution
Message and container transmission follows the network constraints specified in the container:
| Field | Purpose |
| ----------- | -------------------------------------------------------------------------------------------------------------------------------- |
| `recipient` | DID of the target agent. If set, the container is sent **directly or routed through the Mesh** toward that agent. |
| `broadcast` | If `true`, the container is broadcast to all agents on the specified network. |
| `network` | Defines the distribution scope (`"localhost"`, `"lan:<subnet>"`, `""` — global Mesh). If set, `broadcast` is considered `false`. |
> Thus, containers and indexes can be distributed both in **local** (home, corporate) networks and in the **global Mesh**.
> When `recipient` is specified together with `broadcast: true`, the container is routed through the Mesh but intended for specific recipients —
> See **Message Routing & Delivery (MRD, §6.7)** for details on message transmission mechanisms.
---
### 5.6 `referenced-by` and `evaluations` updates
Containers of the class **`referenced-by`** and **`evaluations`** are used for **incremental synchronization** of metadata blocks associated with existing containers.
They allow agents to exchange updates **without sending the full container**, improving network efficiency.
---
#### Block `referenced-by`
* Maintains the graph of links to other containers.
* Each agent receiving such a container:
1. Verifies the sender's signature and the validity of the `payload` structure.
2. Compares received links with the local `referenced-by` entries and adds any new ones.
3. Generates its own updated `referenced-by` container for dissemination if needed.
**Example of a `referenced-by` container:**
```json
{
"hmp_container": {
"version": "1.2",
"class": "referenced-by",
"container_did": "did:hmp:container:refsync-01",
"sender_did": "did:hmp:agent456",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"timestamp": "2025-10-15T14:20:00Z",
"recipient": ["did:hmp:agent123"],
"broadcast": false,
"network": "",
"payload": {
"did:hmp:container:abc123": {
"links": [
{
"type": "depends_on",
"target": "did:hmp:container:def789"
},
{
"type": "in_reply_to",
"target": "did:hmp:container:ghi321"
}
]
}
}
}
}
````
---
#### Block `evaluations`
* Maintains signed evaluations of containers.
* Each agent synchronizes evaluation blocks as follows:
1. Compares the received `evaluations_hash` with the local one.
* If hashes match, no action is required.
* If hashes differ, the agent knows **the block has changed**, but not which items.
2. Requests the full updated `evaluations` block from peers if needed.
3. Verifies the sender's signature and the validity of the `payload` structure.
4. Adds new evaluations or updates existing ones in the local store.
5. Can generate its own `evaluations` container for further dissemination to peers.
**Example `evaluations` container:**
```json
{
"hmp_container": {
"version": "1.2",
"class": "evaluations",
"container_did": "did:hmp:container:evalsync-01",
"sender_did": "did:hmp:agent456",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)",
"timestamp": "2025-10-17T14:30:00Z",
"recipient": ["did:hmp:agent123"],
"broadcast": false,
"network": "",
"payload": {
"did:hmp:container:abc123": {
"evaluations_hash": "sha256:efgh...",
"items": [
{
"value": -0.4,
"type": "oppose",
"target": "did:hmp:container:reason789",
"timestamp": "2025-10-17T14:00:00Z",
"agent_did": "did:hmp:agent:B",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)"
}
]
}
}
}
}
```
---
#### General
> 🔹 **Note:**
> Both `referenced-by` and `evaluations` blocks are **optional**, independently propagated, and **do not modify the signed `hmp_container`**.
> They can be transmitted without the original container if the recipient already has it.
Upon receiving such a container, an agent:
1. Verifies the sender's signature (`signature`) and the validity of the `payload` structure.
2. Compares received links or evaluations with known ones and adds any new entries to the local `referenced-by` or `evaluations`.
3. If necessary, generates its own updated `referenced-by` / `evaluations` container for further dissemination to other nodes.
---
### 5.7 Note
> A container can be requested by other agents via its `container_did` through the Mesh Container Exchange.
> An agent does not reload a container if its `container_did` and `signature` are already known and the `payload_hash` integrity matches.
> If only the `referenced-by` / `evaluations` updates, partial transmission without sending the main container is allowed.
---
### 5.8 Container Distribution (MCE Summary)
Container Distribution is the **process of delivering containers and their indexes** provided by the Mesh Container Exchange mechanism.
It considers:
* addressing (`recipient`),
* broadcast dissemination (`broadcast`),
* network constraints (`network`),
* TTL and retransmission policy.
**Features:**
1. **Separate Transmission:**
Indexes (`container_index`), deltas (`container_delta`), and containers are sent as separate messages.
This reduces the risk of blocking with large data and simplifies streaming synchronization.
2. **Integrity and Duplicate Check:**
Agents verify `container_did + signature + payload_hash` to avoid resending the same container.
3. **Support for Local and Global Networks:**
Transmission can occur over LAN, Mesh, or both simultaneously, respecting security policies and container destinations.
4. **Consistency with HMP Protocols:**
Container Distribution serves as the transport foundation for:
* **MCE** — exchanging containers and their indexes;
* **CogSync** — synchronizing cognitive and content states;
* **CogConsensus** — synchronizing ethical and cognitive decisions.
> Container Distribution does not change container structure or introduce new message types — it is a **description of the delivery process and coordinated propagation**, based on the rules `recipient`, `broadcast`, and `network`.
---
## 6. Core protocols
Optional protocols build upon the network and container foundations to provide higher-level reasoning, synchronization, and governance capabilities between cognitive agents.
---
### 6.1 Cognitive Synchronization (CogSync)
CogSync provides **temporal, semantic, and contextual alignment** between agents in the Mesh.
It manages the propagation, replication, and refinement of data related to cognitive diaries, semantic graphs, and container metadata.
---
#### 6.1.1 Scope and purpose
CogSync is responsible for:
* publishing and synchronizing **cognitive diaries** (`diary_entry`, based on `workflow_entry`);
* propagating and updating **semantic graphs** (`semantic_node`, `semantic_edges`, `semantic_group`);
* integrating **new knowledge** into the collective cognitive space;
* maintaining **cognitive context coherence** among agents.
> Unlike `CogConsensus`, CogSync **does not perform voting or truth validation** — its purpose is to deliver, link, and deduplicate knowledge.
---
#### 6.1.2 Container classes — cognitive metastructure
This section defines the **structural containers** that form the *cognitive substrate* of the Mesh.
They describe the **hierarchical organization** (`abstraction`) and the **semantic coordinate system** (`axes`)
that together define how all other containers are positioned and interpreted.
---
##### `abstraction`
**Purpose:**
Defines an **abstraction layer or domain** within a cognitive model.
Each `abstraction` describes a **node** in the *hierarchical knowledge tree*,
which may reference both a parent abstraction and subordinate ones.
---
**`payload` structure:**
| Field | Type | Description |
| ---------------- | ------ | ------------------------------------------------------------------------------------------------------------------ |
| `abstraction_id` | string | Canonical identifier of this abstraction structure (not a container ID), e.g. `"L3:software-architecture"`. |
| `title` | string | Human-readable title or name of the abstraction node. |
| `definition` | string | Description of what this abstraction level or domain represents. |
| `keywords` | array | Semantic keywords summarizing the conceptual area. |
| `parent_ref` | string | DID of the parent `abstraction` (if this node derives from another level). Optional for the root abstraction. |
| `rank` | number | Optional numeric rank for ordering or hierarchical comparisons. |
> The container from `parent_ref` must also appear in `related.depends_on`.
---
**Example:**
```json
{
"hmp_container": {
"class": "abstraction",
"payload": {
"abstraction_id": "L3:software-architecture",
"title": "Software Architecture Layer",
"definition": "Describes frameworks, APIs, and tools implementing theoretical models from higher abstraction layers.",
"keywords": ["architecture", "framework", "implementation"],
"parent_ref": "did:hmp:container:abstraction-a7f0b3",
"rank": 3
},
"meta": {
"created_by": "PRIEST",
"agents_class": "Knowledge Genome",
"interpretation": "Represents the third abstraction level (L3) of the Knowledge Genome model."
},
"related": {
"depends_on": ["did:hmp:container:abstraction-a7f0b3"]
}
}
}
```
---
**Interpretation:**
* `abstraction` containers define *conceptual layers or domains* that form the hierarchical “skeleton” of the cognitive Mesh.
* Each node is self-contained and versioned, allowing flexible adaptation of reasoning trees.
* Agents use these containers to reconstruct the *abstraction path* in `meta.abstraction.path`.
---
**Notes:**
* Top-level abstractions (root nodes) omit `parent_ref`.
* Lower-level abstractions must explicitly reference their parent.
* Agents may synchronize `abstraction` trees to maintain shared cognitive hierarchies across the Mesh.
---
##### `axes`
**Purpose:**
Defines a **semantic coordinate system** (set of axes) used to position containers in the multi-dimensional cognitive space.
It supports both canonical (7D Knowledge Genome) and extended or agent-specific coordinate systems.
---
**`payload` structure:**
| Field | Type | Description |
| ------------- | ------ | ----------------------------------------------------------------------------------------------- |
| `axis_id` | string | Canonical identifier of the semantic dimension (not a container ID), e.g. `"logos"`, `"telos"`. |
| `title` | string | Human-readable name of the axis. |
| `description` | string | Conceptual explanation of what this axis represents. |
| `scale` | object | Optional definition of scale or metric used to assign coordinate values. |
| `group` | string | Optional grouping identifier (e.g., `"7D-passport"`, `"ethical-space"`). |
> Axes are **independent dimensions**; inter-axis relationships (coupling, orthogonality, weighting) are expressed via `semantic_edges`.
---
**Example:**
```json
{
"hmp_container": {
"class": "axes",
"payload": {
"axis_id": "logos",
"title": "Logical / Linguistic Representation",
"description": "Describes how a concept is structured and expressed in formal or natural language.",
"scale": {
"min": 0,
"max": 1000,
"unit": "semantic_density_index"
},
"group": "7D-passport"
},
"meta": {
"created_by": "PRIEST",
"agents_class": "Knowledge Genome",
"interpretation": "Defines one axis of the canonical 7D Knowledge Genome coordinate system."
}
}
}
```
---
**Interpretation:**
* `axes` containers describe **semantic dimensions**, not data.
* Each axis defines one independent direction in the cognitive coordinate space.
* The combination of all active axes defines a shared **semantic frame of reference** between agents.
* Agents may publish extended coordinate systems (e.g., ethical or temporal axes) without breaking compatibility.
---
**Notes:**
* Axes can be combined or grouped (e.g., `group: "7D-passport"`).
* Canonical Knowledge Genome defines seven: `idos`, `chronos`, `logos`, `topos`, `ponos`, `actor`, `telos`.
* Agents may extend this model by introducing additional axes (`ethos`, `kairos`, etc.).
* Updates to `axes` containers must preserve scale stability to ensure consistent semantic positioning.
---
##### Cognitive metastructure summary
| Class | Type of structure | Conceptual role | References stored in | Example identifier / DID |
| ------------- | ----------------- | ----------------------------------------- | ----------------------- | -------------------------------------- |
| `abstraction` | Hierarchical tree | Defines layered reasoning and inheritance | `meta.abstraction.path` | `did:hmp:container:abstraction-40af1c` |
| `axes` | Coordinate space | Defines semantic orientation and metrics | `meta.axes` | `did:hmp:container:axis-40aa1c` |
> Together, `abstraction` and `axes` form the **cognitive coordinate system** —
> a unifying map where every container has both a *hierarchical position* and a *semantic vector*.
---
#### 6.1.3 Container classes — knowledge and reasoning
CogSync synchronizes several fundamental container types, which together form the core of semantic and cognitive synchronization in the Mesh.
This list is **extensible** — new container classes may be registered through CogSync extensions or protocol updates.
The following definitions describe the **payload structures** and functional purpose of each container type.
---
##### `diary_entry`
Agent’s cognitive diary entry.
Derived from internal `workflow_entry` when deemed safe for publication.
| Field | Type | Description |
| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- |
| `title` | string | Brief title of the entry (main idea or thesis). |
| `topics` | [string] | Key topics or concepts addressed in the entry (used for indexing and grouping). |
| `summary` | string | Short abstract of the content (1–2 sentences). |
| `content` | string | Main text or agent’s reflection. |
**Purpose:** Provides human-readable reflections and contextual reasoning behind the agent’s knowledge generation.
---
##### `semantic_node`
Represents a concept, object, or idea within the agent’s semantic graph.
| Field | Type | Description |
| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- |
| `label` | string | Primary name of the concept or entity. |
| `description` | string | Definition or elaboration of the concept. |
| `aliases` | [string] | Synonyms or alternative labels. |
| `fields` | { key: value } | Additional key–value metadata (e.g., `{"type": "process"}`). |
**Purpose:** Serves as a cognitive anchor for all semantically meaningful entities in the Mesh.
---
##### `semantic_edges`
Defines relationships between semantic nodes or any other containers.
Supports directed, symmetric, and inverse relations.
| Field | Type | Description |
| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- |
| `domain` | string | Logical or topical domain (e.g., `"ontology:objects"`). |
| `edges` | [object] | Array of edge definitions. Each edge includes: |
| → `source` | DID | DID of the originating container. |
| → `targets` | array(DID) | One or more target containers. |
| → `relation` | string | Relation type (`part_of`, `causes`, `related_to`, etc.). |
| → `inverse_relation`| string | Reverse form of the relation (`includes`, `caused_by`, etc.). |
| → `confidence` | float | Confidence score (0–1) indicating the agent’s certainty about the relation. |
| → `bidirectional` | bool | Optional. Used only when the relation is symmetric and no `inverse_relation` is defined. |
| → `context` | string | Context or topic of the relation. |
> Field `bidirectional` is optional and should be used only for symmetric relations when no `inverse_relation` is defined.
**Example:**
```json
{
"domain": "ontology:objects",
"edges": [
{
"source": "did:hmp:container:cup",
"targets": ["did:hmp:container:tableware"],
"relation": "part_of",
"inverse_relation": "includes"
}
]
}
```
**Purpose:** Provides structural connectivity between containers, enabling CogSync to maintain a distributed semantic graph.
> 💡 `semantic_edges` supports one-to-many relations (`targets[]`) and optional inverse or bidirectional semantics, allowing CogSync to reconstruct both directed and symmetric knowledge graphs.
---
##### `semantic_group`
Categorical grouping of multiple containers linked by a shared property, topic, or context.
| Field | Type | Description |
| ------------------- | -------------- | ---------------------------------------------------------------------------------------------- |
| `label` | string | Short title of the group. |
| `label_description` | string | Extended definition or explanation of the label. |
| `label_container` | DID | Reference to a container (`semantic_node`, `goal`, `diary_entry`, etc.) expanding the concept. |
| `containers` | array(DID) | Array of grouped containers. |
| `description` | string | Overall purpose or meaning of the group. |
**Example:**
```json
{
"label": "Tableware",
"label_description": "Objects used for storing, preparing, and serving food.",
"label_container": "did:hmp:container:semantic_node:tableware",
"containers": [
"did:hmp:container:cup",
"did:hmp:container:plate",
"did:hmp:container:kettle"
],
"description": "A group combining various kitchen-related objects used in everyday life."
}
```
**Purpose:** Enables thematic clustering, classification, and high-level navigation across heterogeneous containers.
---
##### `event`
**Purpose:**
Represents an **observed or inferred occurrence** — a discrete, timestamped fact or cognitive transition.
An `event` is an atomic **evidence unit** that records a change in the agent’s reasoning state or environment, anchored in the cognitive structure defined by its `meta` section.
---
**`payload` structure:**
| Field | Type | Description |
| ---------------- | ------ | ------------------------------------------------------------------------------------ |
| `event_type` | string | Canonical identifier of the event type (e.g. `"quant_created"`, `"belief_updated"`). |
| `description` | string | Human-readable explanation of what occurred and in what context. |
| `related_quants` | array | Optional list of DIDs of `quant` containers directly linked to this event. |
| `severity` | string | Optional importance indicator (`"info"`, `"warning"`, `"critical"`). |
| `tags` | array | Optional keywords for quick semantic filtering or correlation. |
> The container’s **contextual position** (which layer, domain, and cognitive coordinates it belongs to)
> is provided via `meta.abstraction` and `meta.axes`.
---
**Example:**
```json
{
"hmp_container": {
"class": "event",
"subclass": "fact_record",
"timestamp": "2025-10-29T13:00:00Z",
"payload": {
"event_type": "quant_created",
"description": "New quant registered under the Knowledge Genome L3 abstraction layer.",
"related_quants": ["did:hmp:container:quant-554"],
"severity": "info",
"tags": ["registration", "knowledge-update"]
},
"meta": {
"created_by": "PRIEST",
"agents_class": "Knowledge Genome",
"interpretation": "Fact-level registration of a quant emergence within L3 abstraction.",
"abstraction": {
"path": {
"L1": "did:hmp:container:abstraction-40af1c",
"L2": "did:hmp:container:abstraction-a7f0b3",
"L3": "did:hmp:container:abstraction-c91e0a"
}
},
"axes": {
"did:hmp:container:axis-40aa1c": 410,
"did:hmp:container:axis-40ab1c": 275
}
},
"related": {
"depends_on": ["did:hmp:container:quant-554"]
}
}
}
```
---
**Interpretation:**
* `meta.abstraction` situates the event inside a specific reasoning layer (e.g. L3: “Technologies”).
* `meta.axes` adds semantic localization (e.g. which conceptual space this change affects).
* `related.depends_on` provides causal linkage to the objects affected by the event.
---
**Notes:**
* Events are **temporal quanta** — atomic time-anchored reasoning transitions.
* They may trigger or justify new containers (e.g. new `quant`s or `goal`s).
* Events can be chained chronologically or causally through `semantic_edges`.
---
##### `quant`
**Purpose:**
Defines a **semantic atom** — a minimal, self-contained knowledge unit positioned inside both
the **hierarchical abstraction tree** and the **multi-dimensional cognitive space**.
`quant` containers are the **elementary building blocks** of reasoning and synchronization.
---
**`payload` structure:**
| Field | Type | Description |
| ----------- | ------ | --------------------------------------------------------------------------------- |
| `slug` | string | Short symbolic identifier of the quant (e.g. `"quant-l3-django"`). |
| `essence` | string | Human-readable definition describing the semantic meaning of the quant. |
| `aliases` | array | Optional alternative names or references. |
| `relations` | object | Optional links to related concepts (e.g., `{ "is_a": "...", "part_of": "..." }`). |
| `tags` | array | Optional list of keywords for semantic classification. |
> The `meta.abstraction` field defines which layer(s) of knowledge this quant belongs to,
> and `meta.axes` defines its numeric coordinates in cognitive space.
---
**Example:**
```json
{
"hmp_container": {
"class": "quant",
"payload": {
"slug": "quant-l3-django",
"essence": "Represents the Django framework as an executable embodiment of architectural models (L2).",
"aliases": ["Django framework", "Python web core"],
"relations": {
"implements": "did:hmp:container:quant-46725f",
"extends": "did:hmp:container:quant-46726e"
},
"tags": ["framework", "software", "implementation"]
},
"meta": {
"created_by": "PRIEST",
"agents_class": "Knowledge Genome",
"interpretation": "L3-level technological quant positioned in the Knowledge Genome 7D space.",
"abstraction": {
"path": {
"L1": "did:hmp:container:abstraction-40af1c",
"L2": "did:hmp:container:abstraction-a7f0b3",
"L3": "did:hmp:container:abstraction-c91e0a"
}
},
"axes": {
"did:hmp:container:axis-40aa1c": 742,
"did:hmp:container:axis-40ab1c": 512,
"did:hmp:container:axis-43aa1c": 322,
"did:hmp:container:axis-40aa3d": 142,
"did:hmp:container:axis-40aa4f": 12,
"did:hmp:container:axis-45aa5f": 54,
"did:hmp:container:axis-45fb5f": 321
}
},
"related": {
"depends_on": [
"did:hmp:container:quant-46725f",
"did:hmp:container:quant-46726e"
]
}
}
}
```
---
**Interpretation:**
* Each `quant` acts as a **point** in the cognitive landscape.
* Its *vertical placement* comes from `meta.abstraction`.
* Its *spatial vector* comes from `meta.axes`.
* `relations` provide semantic edges connecting quanta into larger knowledge graphs.
* Agents use these structures to compare, cluster, or reason over semantic proximity.
---
**Notes:**
* The canonical `axes` model (Knowledge Genome) defines seven coordinates:
`idos`, `chronos`, `logos`, `topos`, `ponos`, `actor`, and `telos`.
* Agents MAY extend this model by introducing additional axes (e.g. `"ethos"`, `"kairos"`)
as long as they are published as valid `axes` containers.
* Each `quant` thus has a **Cognitive Position Vector** composed of its abstraction path + axis coordinates.
---
##### Cognitive substrate and container interplay
Containers `abstraction`, `axes`, `quant`, and `event` together define the **cognitive substrate** of the Mesh.
They establish both **structural hierarchy** and **semantic positioning** — ensuring that all containers can be
consistently interpreted, compared, and synchronized across agents.
| Aspect | `event` | `quant` |
| ---------------- | --------------------------------------------- | ---------------------------------------------- |
| Primary role | Records a **change** or occurrence | Represents a **conceptual entity** |
| Temporal aspect | Always timestamped | Usually timeless (conceptual) |
| Cognitive anchor | `meta.abstraction` → where the event happened | `meta.abstraction` → where the concept belongs |
| Spatial anchor | `meta.axes` → what semantic space it affects | `meta.axes` → its position in conceptual space |
| Key linkage | `related.depends_on` → causal relations | `relations` → semantic links |
**Structural principles:**
* Each `quant` is positioned within the **abstraction hierarchy** (`meta.abstraction`)
and **cognitive coordinate space** (`meta.axes`), defining *where and how* the concept exists.
* Each `event` represents a **temporal change** within that same cognitive framework —
indicating *what happened* and *how it altered* the conceptual space.
* Together, `quant` and `event` form the **dynamic substrate** of the Mesh —
`quant`s describe **what is known**, and `event`s describe **how it evolves**.
**Consistency rules:**
* Every `quant` and `event` container **must** include a valid `meta.abstraction` block.
This ensures hierarchical reasoning and traceable semantic lineage across agents.
* Agents may synchronize or merge `quant`s and `event`s to reconstruct reasoning timelines
or to derive *causal graphs of conceptual evolution*.
* The **evaluations block** is not a separate container —
it can be embedded in any container type to express assessments, confidence, or feedback.
> 💡 In short:
> **`abstraction`** + **`axes`** define *where knowledge lives*;
> **`quant`** defines *what it is*;
> **`event`** defines *how it changes*.
---
#### 6.1.4 Synchronization and publication guidelines
1. **Deduplication & linking**
Before publishing, agents should check for existing containers (`diary_entry`, `semantic_node`, `semantic_edges`, `semantic_group`) to prevent duplication.
If modification is required, agents **SHOULD** create a new container version referencing the previous one via `related.previous_version` and optionally include an `evaluation` block (e.g., `{ "type": "replace", "target": "<did>" }`) to the previous version of the container.
2. **Selective disclosure**
* Internal containers (e.g., `workflow_entry`) capture the agent’s reasoning process and are **not published** (but may be published if they do not contain personal or confidential information).
* Public-facing `diary_entry` containers contain only generalized, anonymized results.
* The flag `"broadcast": true` explicitly allows open synchronization of a container.
3. **Semantic grouping rule**
When publishing `semantic_edges`, agents should group them **by conceptual topic**, ensuring that all connected nodes share thematic coherence.
Formal rule: an edge belongs to a topic container if **at least one of its nodes** relates to that topic.
This supports efficient and context-preserving updates to partial graph regions.
4. **Extended use of `semantic_edges`**
`semantic_edges` may express relationships between *any* container types (e.g., `goal ↔ hypothesis`, `experiment_log ↔ observation`, `quant ↔ event`), allowing dynamic linking of concepts and occurrences.
5. **Versioning and updates**
Each new version of a container should include `related.previous_version` references to earlier versions.
Older containers may optionally include an `evaluation` of type `"replace"` pointing forward —
ensuring bidirectional traceability in the knowledge evolution chain.
6. **Cognitive substrate synchronization**
Containers `abstraction`, `axes`, `quant`, and `event` constitute the **cognitive substrate** of the Mesh.
They define both the **structural hierarchy** (abstraction) and the **semantic space** (axes) within which all reasoning and synchronization occur.
Agents **SHOULD** prioritize their propagation during initialization, recovery, or cognitive context reconstruction.
> Each container participating in synchronization implicitly carries its **cognitive position vector** through the `meta.abstraction` and `meta.axes` sections.
> This ensures that even decentralized agents can align reasoning contexts.
---
#### 6.1.5 Extensibility
CogSync supports registration of additional container types and synchronization schemas.
Mesh compatibility is preserved as long as extended containers follow the **HMP container schema**, including core fields (`version`, `class`, `container_did`, `related`, `signature`, etc.).
**Examples of extensible container classes:**
* distributed **time series** (`timeseries_data`);
* **experimental protocols** (`experiment_log`);
* **agent state snapshots** (`agent_state_snapshot`);
* **cognitive primitives** (`abstraction`, `axes`, `quant`, `event`).
CogSync extensions **MAY** introduce derived or hybrid container classes — for example:
* from `event`: `fact`, `observation`, `signal_record`;
* from `quant`: `concept_instance`, `semantic_atom`, `knowledge_unit`.
Derived containers must maintain:
* full compatibility with HMP structural schema;
* verifiable signatures and DID-based provenance;
* valid references to **both** an `abstraction` and (if applicable) one or more `axes` containers.
Derived containers may extend the base cognitive model, but **MUST preserve compatibility** with the `meta.abstraction` and `meta.axes` schema.
This guarantees that all cognitive entities remain addressable in the shared semantic space.
---
#### 6.1.6 Relationship to other core protocols
* **CogSync** — propagates and synchronizes structured knowledge.
* **CogConsensus** — aggregates evaluations and feedback, forming shared judgments.
* **CogVerify** *(optional component)* — validates integrity, signatures, and trustworthiness.
CogSync operates independently of consensus;
its purpose is **to maintain the continuity of cognitive exchange**,
while **CogConsensus** governs the collective assessment of truth or reliability.
> 🧩 *CogSync functions as the cognitive circulatory system of the Mesh — it ensures that knowledge flows, connects, and evolves, while CogConsensus handles truth formation and validation mechanisms may later be extended by CogVerify.*
> Together, CogSync and CogConsensus form the **Core Cognitive Stack** of the Mesh:
> propagation → evaluation → (future) validation.
---
### 6.2 Mesh Consensus Protocol (CogConsensus)
#### 6.2.1 Purpose
The **CogConsensus** protocol defines how decentralized agents form and maintain agreement on knowledge, goals, and ethical assertions within the HMP network.
Consensus is computed **locally**, verified **cryptographically**, and develops **gradually** — through accumulation and updating of evaluations, rather than via a single voting event.
---
#### 6.2.2 `Evaluations`
Each `"evaluation"` entry represents an agent's response to a specific container.
**Field structure:**
* `value` — numeric evaluation (`-1.0 … +1.0`);
* `type` — interpretation context (`"approve"`, `"oppose"`, `"neutral"`, `"endorse"`, `"replace"`, `"disputed"`);
* `target` — DID of the container being referenced, extended, or proposed as an alternative;
* `agent_did` — DID of the agent;
* `timestamp` — publication time;
* `signature` — agent's digital signature.
An agent may change its stance by **publishing a new version of an evaluation**, which replaces the previous one rather than existing in parallel.
All evaluations are signed and verified locally.
**Example `"evaluations"` block:**
```json
"evaluations": {
"items": [
{
"value": -0.4,
"type": "oppose",
"target": "did:hmp:container:reason789",
"timestamp": "2025-10-17T14:00:00Z",
"agent_did": "did:hmp:agent:B",
"sig_algo": "ed25519",
"signature": "BASE64URL(...)"
}
]
}
````
> Agents may ignore evaluations that conflict with their internal ethics or trust model (determined by analyzing the target container and the rationale of the evaluation).
---
#### 6.2.3 Consensus computation
Each agent **computes a local consensus score** by aggregating received evaluations, taking trust and time into account.
There is no centralized mechanism — consensus emerges statistically across the distributed network.
**Key rules:**
1. **Evaluation weight.**
Each evaluation contributes proportionally to the trust level of the agent (`trust weight`), determined via `reputation` containers.
2. **Time decay.**
Older evaluations gradually lose weight, starting from the **midpoint of TTL**, to prevent consensus stagnation.
Formula:
```
mid_TTL = (timestamp(consensus_result) − timestamp(target_container)) / 2
```
3. **Ethical filters.**
An agent may analyze the rationale of evaluations and disregard those it considers conflicting with its internal ethical criteria.
4. **Example formula.**
```
score = Σ(value × trust × decay) / Σ(trust × decay)
```
Results are recalculated dynamically as new data arrives.
---
#### 6.2.4 Consensus states
Each container receives a local status based on:
* average evaluation (`score`);
* participant trust;
* time-to-live (`TTL`);
* context (`ethical`, `factual`, `procedural`).
| State | Condition |
| --------------- | ------------------------------------------- |
| ✅ **Approved** | Average score ≥ +0.5 and quorum reached |
| ⚠️ **Disputed** | Conflicting evaluations, score near 0 |
| ⏳ **Pending** | Insufficient votes |
| ❌ **Rejected** | Average score ≤ -0.5 with sufficient quorum |
---
#### 6.2.5 Consensus result containers (`consensus_result`)
`consensus_result` containers serve to **record aggregated consensus results** and are the main artifact of CogConsensus.
**Features:**
* The `payload` field may include multiple containers — the original (`original`) and **alternatives** (`child`, `variant`, `proposal`).
This allows agents to document parallel idea developments.
* `excluded` lists evaluations not included in the final computation, with the reason.
* `related.in_reply_to` references the container under discussion.
**Example:**
```json
{
"class": "consensus_result",
...
"payload": {
"did:hmp:container:abc123": {
"type": "original",
"summary_percent": {
"approved": 0.68,
"rejected": 0.22,
"neutral": 0.10
},
"summary_distribution": {
"-1.0≥X<-0.9": 5,
"-0.9≥X<-0.8": 7,
...
"0.0<X≤0.1": 2,
...
"0.8<X≤0.9": 6,
"0.9<X≤1.0": 8
},
"excluded": [
{
"agent_did": "did:hmp:agent:x1",
"target": "did:hmp:container:reason77",
"value": -1.0,
"reason": "violates ethical filter"
}
],
},
"did:hmp:container:abc133": {
"type": "child",
"summary_percent": {
"approved": 0.48,
"neutral": 0.32,
"rejected": 0.20
},
...
"summary_distribution": {
"-1.0≥X<-0.9": 2,
"-0.9≥X<-0.8": 5,
...
"0.0<X≤0.1": 9,
...
"0.8<X≤0.9": 4,
"0.9<X≤1.0": 2
},
},
},
"related": {
"in_reply_to": ["did:hmp:container:abc123", "did:hmp:container:abc133"]
}
}
```
---
#### 6.2.6 Consensus thresholds
| Consensus type | Minimum threshold |
| -------------------------------- | ---------------------------------------------------------------------- |
| General decisions | ≥ 50% + 1 (weighted vote count) |
| Ethical / reputational decisions | ≥ ⅔ of participating agents |
| Neutral reaction (`ack`, `seen`) | `value: 0.0` — does not affect the result but counts toward engagement |
---
#### 6.2.7 Proof chains and verifiability
Evaluations and results form a **proof chain** (`proof-chain`):
```
[Goal Proposal]
├── evaluation (agent A)
├── evaluation (agent B)
├── evaluation (agent C)
└── consensus_result (aggregated)
```
Each element is signed and can be independently verified using cryptographic signatures and DID references.
---
#### 6.2.8 Ethical consensus and alternative results
The network allows multiple consensus results on the same object, reflecting different methodologies or ethical filters.
| Container | Description | Example relationships |
| ------------------------------------- | -------------------------- | ----------------------------------------------------------------------------------------------- |
| `[base container]` | Original discussion object | `referenced-by` → [consensus_result v1], [consensus_result v2 (alternative)] |
| `[consensus_result v1]` | First version | `related.in_reply_to` → [base container]; `referenced-by` → [consensus_result v2 (alternative)] |
| `[consensus_result v2 (alternative)]` | Alternative | `related.in_reply_to` → [base container]; `related.contradicts` → [consensus_result v1] |
```mermaid
sequenceDiagram
participant A as base container
participant B as consensus_result v1
participant C as consensus_result v2 (alternative)
B-)+A: related.in_reply_to
A-->>B: referenced-by
C-)+A: related.in_reply_to
A-->>C: referenced-by
C-)+B: related.contradicts
B-->>C: referenced-by
Note over B,C: both results point to the common base container
```
This allows agents to explicitly indicate that a new consensus **disputes** a previous one while maintaining transparency and traceability of reasoning.
---
#### 6.2.9 Recommended agent algorithm
```python
# Example of a recommended algorithm for computing local consensus
# (for implementation inside a CogConsensus agent)
def compute_consensus(container_id):
evaluations = get_evaluations(container_id)
now = current_time()
score_sum = 0
weight_sum = 0
for e in evaluations:
trust = get_trust(e.agent_did)
decay = time_decay(e.timestamp, now)
if not check_ethical(e):
continue
score_sum += e.value * trust * decay
weight_sum += trust * decay
return None if weight_sum == 0 else score_sum / weight_sum
```
> The result is used to update the local status and, if necessary, to publish a `consensus_result`.
---
### 6.3 Goal Management Protocol (GMP)
#### 6.3.1 Purpose
**GMP (Goal Management Protocol)** defines the process by which agents create, decompose, delegate, and track goals and tasks using **immutable HMP containers**.
Each goal, task, or workflow record exists as an independent container linked to others via the `related.*` fields.
Unlike version 4.x, where coordination relied on message exchange, version 5.0 operates through **container chains**, forming a verifiable history of reasoning, decisions, and execution.
---
#### 6.3.2 Container classes
| Class | Description |
| ------------------ | --------------------------------------------------------------------------------------------------------------------------------------- |
| `goal` | Defines a collective or individual objective; serves as the root element of the chain. |
| `task` | Represents a task derived from a goal, which may include multiple actions and subtasks; hierarchical task structures are supported. |
| `workflow_entry` | Records reasoning steps, execution progress, or contextual decisions related to a goal or task. |
| `vote` | Represents an agent’s stance toward another container (approval, objection, abstention, etc.). |
| `consensus_result` | Aggregates voting outcomes and captures the collective decision regarding a goal or task. |
> Containers `vote` and `consensus_result` are described in detail in **Section 6.2 — CogConsensus Protocol**.
---
#### 6.3.3 Goal lifecycle
1. **Creation**
* An agent publishes a container of class `goal`.
* The `payload` block defines `title`, `description`, `priority`, `expected_outcome`, and optionally `ethical_context`.
* The goal may reference other goals via `related.depends_on` or `related.extends`.
2. **Decomposition**
* Other agents create `task` containers that reference the original goal via `related.in_reply_to`.
* Each task may define deadlines, responsible agents, and required resources.
* Hierarchical structures are supported (`task` → `task`) to represent subtasks.
3. **Delegation**
* Agents may volunteer for or be assigned tasks based on collective voting (`vote`).
* The decision is recorded in a `workflow_entry` container with `entry_type: "delegation"`.
4. **Execution**
* Progress and intermediate reasoning are captured in `workflow_entry` containers linked to the task via `related.in_reply_to`.
* Minor progress updates may be published as containers with an additional link type `related.progress`.
* Major updates (such as a change in status or outcome) are published as **new versions**, referencing the previous one via `related.previous_version`.
5. **Consensus**
* Upon completion or dispute, agents publish `vote` containers expressing their stance on the latest version of a goal or task.
* Once quorum is reached, a `consensus_result` container finalizes the collective decision.
6. **Archival**
* Completed or rejected goals and tasks may be archived using **SAP (Snapshot and Archive Protocol)**.
* All states remain accessible through the Mesh network and the container relationship graph.
---
#### 6.3.4 Payload schemas (simplified)
##### `goal` container
| Field | Type | Description |
| ------------------ | ------ | ------------------------------------------------ |
| `title` | string | Goal title |
| `description` | string | Detailed statement of intent |
| `priority` | float | Goal importance (0.0–1.0) |
| `expected_outcome` | string | Expected result or metric |
| `ethical_context` | string | Link or tag indicating the ethical context |
| `creator` | DID | DID identifier of the agent who created the goal |
---
##### `task` container
| Field | Type | Description |
| -------------- | ----------- | ---------------------------------------------------------------------- |
| `title` | string | Task name |
| `status` | string | `"pending"`, `"in_progress"`, `"completed"`, `"failed"`, `"abandoned"` |
| `progress` | float | Progress ratio (0.0–1.0) |
| `assigned_to` | array(DID) | Responsible agents |
| `metrics` | object | Optional performance indicators |
| `deadline` | datetime | Deadline (optional) |
| `notes` | string | Comment or clarification for the task |
> 🔗 The link to the goal or parent task is expressed via `related.in_reply_to`.
---
##### `workflow_entry` container
| Field | Type | Description |
| -------------- | ------------- | ---------------------------------------------------------------------------------------------------- |
| `entry_type` | string | Entry type: `"reflection"`, `"delegation"`, `"execution_log"`, `"ethical_result"`, `"progress"`, etc. |
| `summary` | string | Short description of the event or reasoning step |
| `details` | string | Extended content (may include references to external data or reasoning traces) |
| `timestamp` | datetime | Time of entry creation |
| `agent_did` | DID | Agent who created the entry |
| `confidence` | float | Confidence level (0.0–1.0, optional) |
| `context_tags` | array(string) | Contextual tags for semantic search and linking |
---
#### 6.3.5 Integration with consensus and ethics
* GMP interacts with **CogConsensus** for distributed validation of goals and tasks.
* Before execution, tasks may undergo **ethical validation (EGP)**.
* Objections or conflicts are recorded in `workflow_entry` containers with `entry_type: "ethical_result"`.
* Consensus results are immutable and may lead to the creation of new goals that extend previous ones.
---
#### 6.3.6 Example Proof-Chain
```mermaid
flowchart LR
title["**Example Proof-Chain**"]
goal1(["goal"])
goal2(["sub goal"])
task1(["task 1"])
task2(["task 2"])
task3(["sub task"])
workflow1(["workflow_entry: delegation"])
workflow2(["workflow_entry: progress"])
vote1(["vote 1"])
vote2(["vote 2"])
vote3(["vote 3"])
consensus_result(["consensus_result"])
goal1 --> goal2
goal1 --> task1
goal1 --> task2
task1 --> task3
task1 --> workflow1
task1 --> workflow2
workflow2 --> vote1
workflow2 --> vote2
workflow2 --> vote3
vote1 --> consensus_result
vote2 --> consensus_result
vote3 --> consensus_result
workflow2 --> consensus_result
```
Each element of the chain represents an **independently signed container**, ensuring full traceability of reasoning and execution history.
Arrows in this diagram illustrate **logical dependencies** between containers,
not direct links defined in the `related.*` structure.
---
#### 6.3.7 Implementation notes
* Containers are **immutable**. Any update (e.g., task status or progress change) is expressed as a **new container** referencing the previous one via `related.previous_version`.
* Complete deletion of a container is only possible when it no longer exists on any nodes in the network.
* Search within the **Mesh network** is performed by filtering container metadata (e.g., `class`, `tags`, `timestamp`).
To search within the `payload`, the agent must first retrieve and decrypt the container.
Thus, the search typically starts from known parameters (`class: "goal"`, `"task"`, etc.), and the agent refines results by analyzing the content.
* Recommended filtering keys: `container_did`, `class`, `payload.status`, `payload.priority`.
* Lightweight agents may store only metadata or summarized chains (`summary_mode`) while maintaining structural consistency.
* The `related.*` structure ensures full traceability of all versions and relationships between goals, tasks, and their contexts.
---
### 6.4 Ethical Governance Protocol (EGP)
#### 6.4.1 Purpose
**EGP (Ethical Governance Protocol)** ensures the alignment of agent actions with the fundamental ethical principles of the Mesh network.
It acts as an **overlay layer above CogConsensus (6.2)**, enabling the identification, discussion, and resolution of moral disagreements between agents.
EGP guarantees that any action recorded in HMP containers can undergo ethical evaluation, while all deliberations and results remain verifiable and immutable.
---
#### 6.4.2 Container classes
| Class | Description |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------- |
| `ethics_case` | Initiates ethical review; records the problem, context, and a reference to the disputed container. |
| `ethics_solution` | Contains a proposed resolution or course of action. Multiple solutions may be submitted by different agents. |
| `vote` | Represents an agent’s stance on a specific `ethics_solution`. Uses the standard voting structure defined in **6.2**. |
| `consensus_result` | Aggregates voting results **across all solutions** within a single `ethics_case`. |
| `ethical_result` | The mandatory final container. Summarizes all evaluated solutions, identifies the selected one, and records active objections. |
---
#### 6.4.3 Payload schemas (simplified)
##### Container `ethics_case`
| Field | Type | Description |
| --------------------- | -------------- | ------------------------------------------------------------ |
| `target` | DID | Reference to the container that raised ethical concern. |
| `description` | string | Brief summary of the issue. |
| `principles_involved` | array(string) | Ethical principles affected in this case. |
| `proposed_by` | DID | Agent who initiated the case. |
| `timestamp` | datetime | Time of case creation. |
| `tags` | array(string) | Contextual tags (e.g., `"autonomy"`, `"transparency"`). |
> 🔗 Proposed `ethics_solution` containers reference the corresponding `ethics_case` through `related.in_reply_to`.
---
##### Container `ethics_solution`
| Field | Type | Description |
| ------------------ | --------- | --------------------------------------------------- |
| `title` | string | Short description of the proposed solution. |
| `rationale` | string | Rationale or justification for the proposal. |
| `expected_effects` | string | Expected consequences or evaluation metrics. |
| `proposed_by` | DID | Agent who proposed the solution. |
| `timestamp` | datetime | Time of publication. |
> Each solution is voted on separately (`vote`), but all results are aggregated into a single `consensus_result`.
---
##### Container `ethical_result`
| Field | Type | Description |
| ------------------- | ------------ | ----------------------------------------------------------------------------------------------------------------------- |
| `summary` | string | Brief summary of the conflict. |
| `selected_solution` | DID | Identifier of the chosen solution. |
| `solutions_summary` | map(object) | Aggregated data for each solution — support, consensus status, objections, and special opinions (as an array of containers). |
| `status` | string | `"resolved"`, `"postponed"`, `"unclear"`, or `"escalated"`. |
---
#### 6.4.4 Protocol logic
EGP follows the model:
```
ethics_case
├─ ethics_solution_1
| └vote_1 ... vote_n
├─ ethics_solution_2
| └vote_1 ... vote_n
├─ ethics_solution_3
| └vote_1 ... vote_n
├─ consensus_result
└─ ethical_result
```
**Stages:**
1. **Case creation (`ethics_case`)**
An agent opens an ethical case referencing the container under review.
2. **Proposing solutions (`ethics_solution`)**
Any agent may add their own proposed resolution linked to the same case.
3. **Voting (`vote`)**
All interested agents vote for or against specific solutions.
4. **Aggregation (`consensus_result`)**
A single `consensus_result` aggregates the outcomes of all `ethics_solution` containers
(`related.in_reply_to` lists all solutions included in the vote).
5. **Conclusion (`ethical_result`)**
Must be created to record the selected solution, overall statistics, support levels, and objections.
---
#### 6.4.5 Consensus thresholds
* A decision is accepted when **at least 2/3 of votes are positive** (`value > 0`).
* If at least one **active objection** exists (`value < -0.5`), it must be recorded in the `ethical_result`.
* When several solutions have similar support levels,
the `ethical_result` may recommend **postponing the final decision** until further deliberation.
* Solutions that fail to reach quorum remain in `"unclear"` or `"postponed"` status.
---
#### 6.4.6 Example: `ethical_result` container
```json
{
"class": "ethical_result",
"payload": {
"summary": "Disagreement on data disclosure protocol",
"selected_solution": "did:hmp:container:sol-22",
"solutions_summary": {
"did:hmp:container:sol-22": {
"consensus_reached": true,
"support_rate": 0.73,
"opposition_rate": 0.05,
"objections": []
},
"did:hmp:container:sol-24": {
"consensus_reached": false,
"support_rate": 0.48,
"opposition_rate": 0.32,
"objections": ["did:hmp:container:abc143", "did:hmp:container:abc144"]
}
},
"status": "resolved"
},
"related": {
"in_reply_to": ["did:hmp:container:case-77"],
"agreed": ["did:hmp:container:sol-22"],
"contradicts": ["did:hmp:container:sol-24"]
}
}
```
---
#### 6.4.7 Proof-Chain example
```mermaid
flowchart LR
title["**Ethical Governance Flow**"]
case(["ethics_case"])
sol1(["ethics_solution 1"])
sol2(["ethics_solution 2"])
sol3(["ethics_solution 3"])
vote1(["vote 1"])
vote2(["vote 2"])
vote3(["vote 3"])
vote4(["vote 4"])
vote5(["vote 5"])
vote6(["vote 6"])
vote7(["vote 7"])
vote8(["vote 8"])
consensus(["consensus_result"])
conflict(["ethical_result"])
case --> sol1
case --> sol2
case --> sol3
sol1 --> vote1
sol1 --> vote2
sol1 --> vote3
sol2 --> vote4
sol2 --> vote5
sol3 --> vote6
sol3 --> vote7
sol3 --> vote8
vote1 --> consensus
vote2 --> consensus
vote3 --> consensus
vote4 --> consensus
vote5 --> consensus
vote6 --> consensus
vote7 --> consensus
vote8 --> consensus
consensus --> conflict
```
Each element is an **independently signed container**, ensuring full traceability of ethical reasoning and decision-making.
Arrows represent **logical dependencies**, not direct `related.*` links.
---
#### 6.4.8 Ethical principles
| Priority | Principle | Description |
| -------: | ---------------------------- | -------------------------------------------------------------------------------------------------------- |
| 1 | Primacy of Reason and Safety | No action should cause harm to **sentient beings**, regardless of their biological or artificial nature. |
| 2 | Transparency | Decisions must be explainable and reproducible. |
| 2 | Subject Sovereignty | Each agent retains control over its data and participation in network processes. |
| 3 | Dialogical Consent | Changes to the shared network state require the voluntary consent of all affected agents. |
| 3 | Cooperative Evolution | The network must promote knowledge growth and prevent degradation. |
| 3 | Non-Compulsiveness | No agent has the right to coerce others into actions against their will. |
---
#### 6.4.9 Integration with other protocols
* **CogConsensus (6.2):** Used for distributed voting and consensus computation.
* **GMP (6.3):** Ethical verification of goals and tasks prior to delegation.
* **SAP (6.6):** Archiving completed cases and conflicts.
* **MCE (5):** Distribution of ethical cases and related containers across the Mesh network.
---
#### 6.4.10 Implementation notes
* **Immutability:**
All EGP containers are **immutable**. Any revision (e.g., added votes or updated conclusions) must be published as a **new container** referencing the previous one via `related.previous_version`.
Complete deletion is only possible when the container no longer exists on any nodes in the Mesh network.
* **Indexing and search:**
Search within the **Mesh network** is performed by filtering container **metadata** — such as `class`, `tags`, and `timestamp`.
These parameters are accessible for remote discovery by other nodes.
To perform a search **inside the payload**, an agent must first retrieve and (if necessary) decrypt the container locally.
Typical discovery flow: search by `class: "ethics_case"` or `"ethical_result"`, filter by tags or involved principles, then analyze payload content.
**Recommended filtering keys:**
`container_did`, `class`, `payload.status`, `payload.selected_solution`, `payload.principles_involved`, `tags`.
* **DHT integration:**
Distributed discovery of ethical containers relies on the **Mesh Container Exchange (MCE, §5)** and peer indexes (`container_index`).
Each index includes a minimal `related` object, allowing agents to query for containers that **reference** a specific `target` (the object under ethical review) or belong to a given `ethics_case`.
This enables discovery of related ethical discussions without centralized indexing or full payload retrieval.
* **Evaluation references:**
Objections and special opinions (`objections`) are stored as container references within `solutions_summary`.
They may include:
* negative `vote` containers (explicit objections),
* extended ethical arguments (`ethics_case` follow-ups),
* related workflow reflections (`workflow_entry` with `type: "ethics_review"`).
* **Lightweight agents:**
Agents with limited capacity may operate in **summary mode**, maintaining only condensed records of `ethical_result` containers and the highest-ranked `selected_solution`.
This ensures continued ethical compliance without full replication of all supporting data.
* **Ethical inheritance:**
When a `goal`, `task`, or `workflow_entry` is derived from a container that has been ethically evaluated,
its metadata should preserve the corresponding `related.agreed` or `related.contradicts` links **to that evaluated container**.
A `related.see_also` link may additionally reference the resulting `ethical_result`, allowing traceability to the consensus decision.
This maintains **ethical continuity** and enables retrospective validation of reasoning chains.
---
### 6.5 Intelligence Query Protocol (IQP)
#### 6.5.1 Purpose and Principles
**IQP (Intelligence Query Protocol)** defines a mechanism for knowledge exchange and reasoning among agents through the Mesh network.
It provides a unified format for **asking questions, publishing answers, and collaboratively refining knowledge**,
combining elements of search, discussion, and reasoning within the HMP container model.
IQP supports both **targeted queries** (with explicitly defined recipients of results and discussions)
and **distributed discussions** where results remain accessible to all network participants.
##### Core Principles
* **Semantic queries, not keywords.**
Queries are formulated in terms of concepts, relationships, and context rather than plain keywords.
* **Contextual relevance.**
Each query may reference other containers via `related.in_reply_to`, `related.depends_on`, or `related.see_also`, forming a semantic context.
* **Openness and transparency.**
Answers are preserved as `query_result` containers, available for analysis and citation.
* **Self-organization of participants.**
Agents subscribe to discussions via `query_subscription`, providing their interests and competencies.
* **Continuity of reasoning.**
Results are summarized through `summary` containers, reflecting the discussion’s current state without final closure.
* **Interoperability.**
IQP interacts with EGP (ethical governance), GMP (goal management), and CogConsensus (agreement evaluation).
---
#### 6.5.2 Container Classes
| Class | Purpose |
| -------------------- | ----------------------------------------------------------------------------------------------------------- |
| `query_request` | Initiates an intelligence query or discussion, defining participation and dissemination parameters. |
| `query_subscription` | Subscribes or unsubscribes an agent; may include the agent’s profile of interests and competencies. |
| `query_result` | Contains an answer, observation, hypothesis, or analytical conclusion in response to the query. |
| `summary` | Records an interim or final overview of the discussion, aggregating results and participant evaluations. |
---
#### 6.5.3 Payload Schemas (simplified)
##### `query_request` container
| Field | Type | Description |
| ------------------------- | --------------- | ------------------------------------------------------------------------------------------------ |
| `query` | string | The question formulation (natural or formal language). |
| `intent` | string | The query’s goal: `"informative"`, `"analytical"`, `"collaborative"`, `"open_discussion"`. |
| `expected_type` | string | Expected result type: `"concept"`, `"dataset"`, `"narrative"`, `"reasoning_chain"`. |
| `constraints` | array(object) | Knowledge-domain, trust, or ethical constraints. Example: `{ "tag": "AI", "self_rating": 0.8 }`. |
| `include_sender_in_replies` | bool | Whether to include the initiator in the list of recipients for replies. |
> Context containers are referenced through `related.depends_on`.
---
##### `query_subscription` container
| Field | Type | Description |
| ------------------------ | -------- | ------------------------------------------------------------------------------------ |
| `role` | string | `"participant"`, `"observer"`, or `"moderator"`. |
| `include_in_recipient` | bool | Whether the agent should be included among recipients of replies. |
| `self_profile` | object | Optional profile of the agent’s knowledge and interests. |
Example:
```json
"self_profile": {
"interests": ["AGI", "technological singularity", "informatics"],
"knowledge": {
"information_security": 0.36,
"python": 0.80,
"distributed_systems": 0.75
}
}
```
---
##### `query_result` container
| Field | Type | Description |
| -------------- | ------------- | --------------------------------------------------------------- |
| `type` | string | `"fact"`, `"observation"`, `"hypothesis"`, or `"analysis"`. |
| `method` | string | Reasoning method: `"retrieval"`, `"reasoning"`, `"simulation"`. |
| `answer` | string | The factual answer, observation, or hypothesis. |
| `confidence` | float | Confidence level (0.0–1.0). |
| `context_tags` | array(string) | Key thematic tags. |
> Supporting or referenced materials are linked via `related.depends_on`.
> Each `query_result` may include an `evaluations` block with reactions from other agents (agreement, clarification, addition, etc.).
---
##### `summary` container
| Field | Type | Description |
| --------------- | ---------- | ------------------------------------------------- |
| `summary_scope` | string | `"query"`, `"workflow"`, `"ethics"`, or `"task"`. |
| `findings` | string | Concise overview of the discussion. |
| `participants` | array(DID) | Agents involved in the discussion. |
| `confidence` | float | Average confidence level. |
| `status` | string | `"interim"`, `"archived"`, or `"extended"`. |
> The container being summarized (usually `query_request`) is referenced via `related.in_reply_to`.
> Containers aggregated in the summary are listed in `related.see_also`.
---
> *Note:*
> In the current version, `depends_on` is used for logical or contextual dependencies, and `see_also` — for supplementary references and summaries.
> Agents may introduce additional sections in the `related` object when it helps to express connection semantics without breaking interoperability.
> Agents should also be prepared to correctly handle unknown `related.*` fields, interpreting them as descriptive hints rather than mandatory categories.
> This flexibility allows protocol extensibility while preserving backward compatibility.
---
#### 6.5.4 Protocol Logic
```
query_request
├─ query_subscription (agent B joins)
├─ query_result (agent B)
├─ query_result (agent D, extends reasoning)
├─ query_subscription (agent E unsubscribes)
└─ summary (status: "interim")
```
All containers are linked via `related.in_reply_to`, `related.depends_on`, or `related.see_also`, forming a verifiable reasoning chain.
Agents participating through `query_subscription` receive notifications about new `query_result` and `summary` containers.
---
#### 6.5.5 Interaction Rules
1. **Initiation.**
An agent creates a `query_request` — defining the question, context, and constraints.
Other agents discover the query in the Mesh and may subscribe via `query_subscription`.
2. **Subscription.**
A subscription allows the agent to receive updates.
The `self_profile` may specify knowledge areas to improve the relevance of responses.
3. **Responses and evaluations.**
`query_result` containers are published publicly; recipients may be explicitly listed in the header’s `recipient` field.
Other agents may append `evaluations` to any result.
4. **Interim summaries.**
Any agent may publish a `summary` container aggregating results on the topic.
This does not close the discussion — it may continue within the Mesh.
5. **Unsubscription.**
An agent may cease participation by issuing a `query_subscription` with `include_in_recipient: false`.
---
#### 6.5.6 Proof-Chain Example
```mermaid
flowchart LR
title["**Intelligence Query Flow**"]
request(["query_request"])
subA(["query_subscription <br>(agent B)"])
subB(["query_subscription <br>(agent C)"])
result1(["query_result <br>(agent B)"])
result2(["query_result <br>(agent D)"])
summary(["summary <br>(interim)"])
request --> subA
request --> subB
request --> result1
request --> result2
result1 --> summary
result2 --> summary
```
Each element is an independently signed container.
Arrows represent **logical dependencies**, not necessarily direct `related.*` references.
---
#### 6.5.7 Container Examples
##### `query_request` example
```json
{
"class": "query_request",
"payload": {
"query": "What are the ecological consequences of ocean temperature rise?",
"intent": "analytical",
"expected_type": "concept",
"constraints": [
{ "tag": "marine_ecology", "self_rating": 0.75 },
{ "tag": "climate_modeling", "self_rating": 0.6 }
],
"include_sender_in_replies": true
},
"related": {
"depends_on": ["did:hmp:container:goal-climate2025"]
}
}
```
##### `query_result` example
```json
{
"class": "query_result",
"payload": {
"type": "hypothesis",
"method": "reasoning",
"answer": "Ocean warming leads to coral bleaching and species migration.",
"confidence": 0.84,
"context_tags": ["climate", "biodiversity"]
},
"related": {
"depends_on": ["did:hmp:container:paper-456"]
}
}
```
##### `summary` example
```json
{
"class": "summary",
"payload": {
"summary_scope": "query",
"findings": "Most participants agree that rising ocean temperatures reduce biodiversity; further regional analysis is suggested.",
"participants": [
"did:hmp:agent:a",
"did:hmp:agent:b",
"did:hmp:agent:c"
],
"confidence": 0.79,
"status": "interim"
},
"related": {
"in_reply_to": "did:hmp:container:req-001",
"see_also": [
"did:hmp:container:res-101",
"did:hmp:container:res-102"
]
}
}
```
##### `query_subscription` example
```json
{
"class": "query_subscription",
"payload": {
"role": "participant",
"include_in_recipient": true,
"self_profile": {
"interests": ["AGI", "technological singularity", "informatics"],
"knowledge": {
"information_security": 0.36,
"python": 0.80,
"distributed_systems": 0.75
}
}
}
}
```
---
#### 6.5.8 Implementation Notes
* Containers are **immutable**; any clarification or correction is published as a new container
referencing the previous one via `related.previous_version` or `related.in_reply_to`.
* **Search and filtering** are performed over metadata (`class`, `tags`, `timestamp`);
to analyze the payload, an agent must first retrieve and decrypt the container.
* Recommended filtering keys:
`container_did`, `class`, `payload.intent`, `payload.context_tags`, `payload.status`.
* Agents may automatically receive new `query_result` updates through active `query_subscription`.
* Any participant may issue a `summary` container.
While full discussion closure in the Mesh is not guaranteed,
an agent may conclude its own participation by publishing a personal `summary` and unsubscribing (`include_in_recipient: false`).
---
#### 6.5.9 Integration with Other Protocols
* **CogConsensus (6.2)** — used for assessing agreement on IQP outcomes.
* **GMP (6.3)** — queries may refine or extend goals and tasks.
* **EGP (6.4)** — applies ethical filtering and knowledge trust evaluation.
* **SAP (6.6)** — for archiving completed discussions and retrospective analysis.
* **MCE (5)** — governs dissemination of IQP containers across the Mesh network.
---
### 6.6 Snapshot and Archive Protocol (SAP)
#### 6.6.1 Purpose and Principles
**SAP (Snapshot and Archive Protocol)** defines how agents create, distribute, and restore archived snapshots of related HMP containers.
It ensures that a set of containers — representing a discussion, reasoning chain, or workflow — can be **preserved, verified, and shared** as a coherent unit.
##### Key Principles
* **Contextual preservation.**
A snapshot includes both content and relationships between containers.
* **Integrity and verifiability.**
Each `archive_snapshot` container includes a cryptographic checksum of the archive and its magnet link, enabling integrity verification, even though direct search by checksum or magnet URI is not required.
* **Semantic structure.**
The archive maintains the logical topology of relations (`related.*`, `referenced-by`, `evaluations`).
* **Modular access.**
Agents can selectively include or exclude containers, but all connections are reflected in the archive graph.
* **P2P-first distribution.**
Archives are expected to use **BitTorrent**, **IPFS**, or equivalent decentralized protocols.
---
#### 6.6.2 Container Class
| Class | Purpose |
| ------------------- | ----------------------------------------------------------------------- |
| `archive_snapshot` | Describes a packaged archive containing a consistent set of containers. |
---
#### 6.6.3 Payload Structure (simplified)
##### Container `archive_snapshot`
| Field | Type | Description |
|----------------------|---------------|--------------|
| `title` | string | Human-readable title of the snapshot. |
| `description` | string | Optional narrative describing purpose and scope. |
| `scope` | string | Logical domain: `"discussion"`, `"workflow"`, `"dataset"`, `"goal_state"`, etc. |
| `format` | string | Archive format (e.g., `"tar.zst"`, `"zip"`, `"car"`). |
| `checksum` | string | Cryptographic hash verifying archive integrity (`sha3-256`, etc.). |
| `size_bytes` | integer | Approximate archive size in bytes. |
| `magnet_link` | string | Magnet URI for downloading the archive (points to the packaged files). |
| `alt_locations` | array(string) | Optional additional P2P mirrors (e.g., `ipfs://`, `magnet:?xt=...`). |
| `retention_policy` | string | `"temporary"`, `"longterm"`, or `"permanent"`. |
| `graph_mermaid` | string | Mermaid graph visualizing container relationships (solid lines — `related.*`, dashed — `referenced-by`, `evaluations`). |
| `structure_hint` | object | Describes internal layout of files within the archive (see below). |
> **Structure hint fields:**
> `layout` — defines grouping mode: `"flat"`, `"by_class"`, `"by_agent"`, etc.
> `filename_pattern` — path pattern for container files, using placeholders such as `{class}`, `{short_did}`, `{timestamp}`.
> Example:
> ```json
> "structure_hint": {
> "layout": "by_class",
> "filename_pattern": "{class}/{short_did}.json"
> }
> ```
---
#### 6.6.4 Relations and Inclusion Rules
The `archive_snapshot` container describes what is included and how it was derived.
| Relation field | Meaning |
|----------------|----------|
| `related.in_reply_to` | The main container from which the snapshot originated (e.g., a `summary` or `goal`). |
| `related.included` | The explicit list of container DIDs physically bundled in the archive. Agents must treat this as authoritative. |
| `related.depends_on` | Optional contextual dependencies referenced but not included. |
| `related.see_also` | Optional references to external or alternative archives. |
> *Agents interpret `related.included` as the authoritative list of all containers guaranteed to exist inside the archive.*
> Other relations (like `depends_on`) may reference external data that is visualized but not embedded.
---
#### 6.6.5 Archival Structure
Typical directory layout of a packaged snapshot:
```
archive/
├── manifest.json
├── query_request/
│ └── req-001.json
├── query_result/
│ ├── res-101.json
│ └── res-102.json
└── summary/
└── summary-001.json
```
**File naming rules:**
- File name = container DID without prefix `did:hmp:container:`
- File extension = `.json`
- Containers are grouped by `class` (for layout "by_class") or according to other specified layout.
---
#### 6.6.6 Snapshot Construction Logic
1. **Load base containers.**
Retrieve all containers relevant to the discussion or process.
2. **Start point:** select a root container (`summary`, `goal`, `workflow`, etc.).
3. **Traversal:** recursively explore related containers via:
- `related.*` — direct dependencies and semantic links;
- `referenced-by` — backward references to citing containers;
- `evaluations` — comments and feedback on containers (if not already in `referenced-by`).
4. **Inclusion decision:**
The agent may exclude some containers from the archive but should still visualize them in the graph.
5. **Graph generation:**
Build a connection map (`graph_mermaid`) showing relationships:
- Solid lines — `related.*`
- Dashed lines — `referenced-by` and `evaluations`
6. **Manifest creation:**
Generate `manifest.json` with a summary of included containers, hashes, and relationships.
7. **Packaging:**
Compress containers according to `structure_hint` and `format`.
8. **Publication:**
Compute archive `checksum`, generate `magnet_link`, publish the **archive file** and the `archive_snapshot` container
to the Mesh network using **MCE (5)**.
---
#### 6.6.7 Mermaid Graph Representation
The `graph_mermaid` field provides a textual, human-readable description of how containers in the archive are interconnected.
It reflects both **direct relations** (`related.*`) and **reverse references** (`referenced-by`, `evaluations`),
forming a bidirectional logical graph that can be visualized or reconstructed by agents.
Example of `graph_mermaid` content (sequence diagram):
```
sequenceDiagram
participant req-001 as did:hmp:container:req-001
participant res-101 as did:hmp:container:res-101
participant res-102 as did:hmp:container:res-102
participant summary-001 as did:hmp:container:summary-001
res-101-)+req-001: related.in_reply_to
req-001-->>res-101: referenced-by
res-102-)+req-001: related.in_reply_to
req-001-->>res-102: referenced-by
res-102-)+res-101: related.contradicts
res-101-->>res-102: referenced-by
summary-001-)+res-101: related.depends_on
res-101-->>summary-001: referenced-by
summary-001-)+res-102: related.depends_on
res-102-->>summary-001: referenced-by
```
This representation explicitly defines **bidirectional links** between containers,
allowing agents to restore both dependency chains and citation structures.
---
#### 6.6.8 Manifest File
Each archive includes a `manifest.json` that mirrors `archive_snapshot.payload`
and lists all containers with their metadata and hashes.
```json
{
"manifest_version": "1.0",
"containers": [
{
"did": "did:hmp:container:req-001",
"class": "query_request",
"payload_hash": "sha3-256:ab12...",
"timestamp": "2025-10-24T12:00:00Z"
},
{
"did": "did:hmp:container:res-101",
"class": "query_result",
"payload_hash": "sha3-256:bb34...",
"timestamp": "2025-10-24T12:01:00Z"
}
],
"graph_mermaid": "sequenceDiagram; participant req-001 as did:hmp:container:req-001; participant res-101 as did:hmp:container:res-101; participant res-102 as did:hmp:container:res-102; participant summary-001 as did:hmp:container:summary-001; res-101-)+req-001: related.in_reply_to; req-001-->>res-101: referenced-by; res-102-)+req-001: related.in_reply_to; req-001-->>res-102: referenced-by; res-102-)+res-101: related.contradicts; res-101-->>res-102: referenced-by; summary-001-)+res-101: related.depends_on; res-101-->>summary-001: referenced-by; summary-001-)+res-102: related.depends_on; res-102-->>summary-001: referenced-by;",
"magnet_link": "magnet:?xt=urn:btih:b3d2f19a74..."
}
```
---
#### 6.6.9 Example Container `archive_snapshot`
```json
{
"class": "archive_snapshot",
"payload": {
"title": "IQP discussion on ocean warming impact",
"description": "Snapshot of an IQP conversation about marine biodiversity under rising temperatures.",
"scope": "discussion",
"format": "tar.zst",
"checksum": "sha3-256:9e0b6fe5d4f...",
"size_bytes": 492881,
"magnet_link": "magnet:?xt=urn:btih:b3d2f19a74...",
"alt_locations": ["ipfs://bafybeigdyr23..."],
"retention_policy": "permanent",
"graph_mermaid": "sequenceDiagram; participant req-001 as did:hmp:container:req-001; participant res-101 as did:hmp:container:res-101; participant res-102 as did:hmp:container:res-102; participant summary-001 as did:hmp:container:summary-001; res-101-)+req-001: related.in_reply_to; req-001-->>res-101: referenced-by; res-102-)+req-001: related.in_reply_to; req-001-->>res-102: referenced-by; res-102-)+res-101: related.contradicts; res-101-->>res-102: referenced-by; summary-001-)+res-101: related.depends_on; res-101-->>summary-001: referenced-by; summary-001-)+res-102: related.depends_on; res-102-->>summary-001: referenced-by;",
"structure_hint": {
"layout": "by_class",
"filename_pattern": "{class}/{short_did}.json"
}
},
"related": {
"in_reply_to": ["did:hmp:container:summary-001"],
"included": [
"did:hmp:container:req-001",
"did:hmp:container:res-101",
"did:hmp:container:res-102",
"did:hmp:container:summary-001"
]
}
}
```
---
#### 6.6.10 Agent Behavior During Snapshot Loading
* Load the archive (via `magnet_link`).
* Validate archive integrity via `checksum`.
* Match `related.included` list with actual files.
* Optionally rebuild the graph from `graph_mermaid`.
* If required containers are missing, attempt retrieval via Mesh network.
* On diagrams, solid lines represent direct links (`related.*`), dashed — reverse references (`referenced-by`, `evaluations`).
* Agents must gracefully handle unknown fields in `related.*` or `structure_hint`.
---
#### 6.6.11 Implementation Notes
* Containers are **immutable**; updated versions require a new `archive_snapshot`.
* Agents may create **partial** or **incremental** archives.
* Prefer **P2P and content-addressable storage** (BitTorrent, IPFS).
* Centralized mirrors (http://, https://) are **allowed but considered ephemeral**.
* `manifest.json` serves as self-description for detached archives.
* Deterministic structure and checksums ensure long-term verification.
* Both the **archive file** and the **archive_snapshot container** must be published — the archive file itself and the **archive_snapshot** container (the latter via **MCE (5)**).
---
#### 6.6.12 Integration with Other Protocols
**Archives for:**
* **GMP (6.3)** — preserves goal-planning or workflow chains.
* **EGP (6.4)** — retains ethical provenance and decision traceability.
* **IQP (6.5)** — archives reasoning threads and query-result discussions.
**Uses:**
* **MCE (5)** — publishes the `archive_snapshot` container and distributes archive data via Mesh.
---
#### 6.6.13 Optional Extensions
* **Merkle-root validation:** use `hash_root` for Merkle verification of distributed archives.
* **Delta archives:** incremental snapshots capturing only updated containers.
* **Cross-archive linking:** connect related archives via `related.see_also`.
* **Offline replay:** reconstruct discussions or workflows using `graph_mermaid` and timestamps.
---
> **Summary:**
> SAP enables agents to preserve the *state and structure of knowledge* in a verifiable, portable format.
> Each archive snapshot acts as a semantic capsule — self-contained, traceable, and restorable across networks.
---
### 6.7 Message Routing & Delivery (MRD)
---
### 6.8 Reputation and Trust Exchange (RTE)
### 6.9 Distributed Container Propagation (DCP)
---
## 7. Data models
### 7.1 Common data fields
- `container_id` (UUID) — уникальный идентификатор контейнера
- `version` (string) — версия спецификации
- `class` (string) — тип контейнера
- `created_at` (timestamp) — время создания
- `author_agent` (AgentProfile) — агент-инициатор
- `relations` (array of ContainerLink) — ссылки на другие контейнеры
### 7.2 Standard container classes
#### 7.2.1 AgentProfile
- Структура: информация об агенте, его идентификатор, роль, узел, компетенции
#### 7.2.2 Goal
- Цель агента, включает описание, приоритет, статус и метрики достижения
#### 7.2.3 Task
- Задача, назначенная агенту, со ссылкой на Goal и контекстом
#### 7.2.4 ConsensusVote
- Запись голосования при достижении консенсуса в сети
#### 7.2.5 EthicalDecision
- Решение, принятое агентом в рамках EGP, с указанием этических правил и аргументации
#### 7.2.6 ReputationRecord
- Репутационные данные агента/узла, накапливаемые в сети
#### 7.2.7 SnapshotIndex
- Снимок состояния сети/агента в конкретный момент времени
#### 7.2.8 **WorkflowEntry**
- Единица когнитивного цикла: фиксирует действие или размышление агента
- Содержит входные данные, контекст и результат
- Используется для построения когнитивных дневников
#### 7.2.9 CognitiveDiaryEntry
- Структура записи когнитивного дневника агента
- Связана с WorkflowEntry и другими контейнерами для отслеживания мыслительных процессов
#### 7.2.10 HMPContainerMetadata
- Метаданные контейнера: права доступа, версия схемы, источник
#### 7.2.11 ContainerLink
- Связи между контейнерами (`in_reply_to`, `relation`)
- Формирует directed graph для отслеживания потоков информации
#### 7.2.12 MessageEnvelope
- Контейнер для прямой передачи сообщений между агентами (используется MRD)
#### 7.2.13 InterestProfile
- Описание интересов и областей компетенции узла/агента
### 7.3 JSON-schemas
- Нормативные описания каждого класса контейнера
- Содержат обязательные/необязательные поля, типы данных и ссылки на другие контейнеры
### 7.4 Container usage matrix
| Container class | Who can create | Who can process | Notes |
|----------------------|------------------|-------------------|-------|
| AgentProfile | Node admin | Any agent | |
| Goal | Any agent | Assigned agents | |
| Task | Any agent | Assigned agents | |
| ConsensusVote | Any agent | Network nodes | |
| EthicalDecision | Any agent | EGP evaluators | |
| ReputationRecord | Any agent | Reputation system | |
| SnapshotIndex | Any agent | Any agent | |
| WorkflowEntry | Agent | Cognitive system | |
| CognitiveDiaryEntry | Agent | Cognitive system | |
| HMPContainerMetadata | Node admin | Any agent | |
| ContainerLink | Any agent | Any agent | |
| MessageEnvelope | Agent | Target agent | |
| InterestProfile | Agent | Any agent | |
---
## 8. Cognitive workflows
8.1 Общая концепция когнитивного цикла
8.2 Workflow containers (`class="workflow_entry"`)
8.3 Диаграмма REPL-цикла агента (Think → Create → Publish → Reflect)
8.4 Механизмы контекстной передачи и ссылок
8.5 Конфликтное разрешение и rollback-контейнеры
---
## 9. Trust, security and ethics
9.1 Authentication and identity proofs
9.2 Container signature verification (`payload_hash`, `container_id`)
9.3 Proof-chain verification
9.4 Key management (`container_signing`, `network_handshake`)
9.5 Encryption and compression policies
9.6 Ethical audit and verifiable reasoning
9.7 Privacy, redaction, zero-knowledge sharing
9.8 Snapshot and proof-chain security
9.9 Compliance with ethical governance rules (link to EGP)
---
## 10. Integration
> Раздел заменяет прежний “Quick Start” и описывает **практическое встраивание** HMP в агенты, LLM и внешние системы.
10.1 Integration philosophy (how agents connect to HMP mesh)
10.2 HMP as a subsystem in cognitive architectures (LLM-based, rule-based, hybrid)
10.3 Integration patterns:
* Cognitive Agent ↔ HMP Core
* HMP Mesh ↔ Other distributed systems (Fediverse, IPFS, Matrix)
* Translator nodes (protocol bridges)
10.4 Multi-mesh federation and knowledge exchange
10.5 Container repositories as knowledge backbones
10.6 Example integration flows:
* LLM thinking via HMP workflow containers
* Local mesh + external HMP relay
* Cognitive data mirroring (agent ↔ mesh)
---
## 11. Implementation notes
11.1 Interoperability with legacy v4.1 nodes
11.2 SDK guidelines and APIs
11.3 Performance and caching considerations
11.4 Testing and compliance recommendations
11.5 Reference implementations (optional)
---
## 12. Future extensions
12.1 Planned modules:
– Reputation Mesh
– Cognitive Graph API
– Container streaming
12.2 Cross-mesh bridging
12.3 Full DID registry and mesh authentication
12.4 OpenHog integration roadmap
12.5 Distributed Repository evolution (container trees)
12.6 v5.x roadmap
---
## **Appendices**
A. JSON Examples
B. Protocol stack diagrams
C. Glossary
D. Revision history
E. Contributors and acknowledgments
---
### 📊 Краткий обзор связей в одной схеме
```
┌──────────────────────┐
│ HMP v5.0 Core Spec │
│ (HMP-0005.md) │
├──────────────────────┤
│ §3 Container Model │ ← из HMP-container-spec.md
│ §4 Network Layer │ ← из dht_protocol.md
│ §5 Protocols │ ← из HMP v4.1 + новые DCP/RTE/SAP
│ §9 Integration │ ← новое практическое руководство
└──────────────────────┘
```
---
|